CVE-2018-3810
Exploitation confirmed. First attested on 2023-10-14 by GCVE · kevintel, GCVE · shadowserver.
- Published2018-01-01
- Fixed in3.5
- WeaknessCWE-287
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
Authentication Bypass vulnerability in the Oturia Smart Google Code Inserter plugin before 3.5 for WordPress allows unauthenticated attackers to insert arbitrary JavaScript or HTML code (via the sgcgoogleanalytic parameter) that runs on all pages served by WordPress. The saveGoogleCode() function in smartgooglecode.php does not check if the current request is made by an authorized user, thus allowing any unauthenticated user to successfully update the inserted code.
Timeline
dates in UTC- 2018-01-0106:29CVE publishedNVD
- 2023-10-1414:54Listed as exploited by GCVEGCVE
- 2023-10-1414:54Exploitation first reportedGCVE
- 2026-10-2319:23First public proof of conceptPoC-in-GitHub
- 2026-10-2319:23EPSS crossed 10 %FIRST EPSS
Observed activity
isMalicious corpus · updated 2026-10-23 18:48 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2018-3810?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2018-3810?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 3.5 | < 3.5 | 3.5 | NVD |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
- Update Oturia smart google code inserter to 3.5
Advisories and patches
- wordpress.orgRelease Notes
Detection
read 2026-10-23 19:23 UTC- Nuclei template
- none so far ProjectDiscovery
- Proof-of-concept repositories
- 3 repositories, unverifiedlucad93/CVE-2018-3810cved-sources/cve-2018-3810nth347/CVE-2018-3810_exploit PoC-in-GitHub
Sources
- GCVEexploitation2023-10-14
- NVDCVSS 3.09.8read 2026-10-23
- NVDCVSS 2.07.5read 2026-10-23
- NVDweakness (CWE)CWE-287read 2026-10-23
- FIRST EPSSEPSS score91.3 %read 2026-10-23
- PoC-in-GitHubproof of concept3read 2026-10-23
- Exploit-DBdetectionread 2026-10-23
Technical details
- CVSS v3 Vector
- CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Published
- 2018-01-01
- Last Modified
- 2026-06-17
- NVD status
- Modified
Frequently asked questions
What is CVE-2018-3810?
Is CVE-2018-3810 actively exploited?
What is the CVSS score for CVE-2018-3810?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- For a threat intelligence platform: malware, C2 and ransomware indicators over STIX/TAXII.
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.