Skip to content
Fencer Intel
critical 9.8

CVE-2018-3810 in the critical feed json

Authentication Bypass vulnerability in the Oturia Smart Google Code Inserter plugin before 3.5 for WordPress allows unauthenticated attacke…

published 8y ago modified 4mo ago also EUVD-2018-15599

cvss
9.8
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
91.3%
EPSS 91.3% chance of exploitation in 30 days, percentile 99.8%
public exploits
1
Exploit-DB, plus a Nuclei check

Summary

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.

Patch / fix

  • oturia smart_google_code_inserter 3.5

Is CVE-2018-3810 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Timeline

  1. Published
  2. First public exploit (EDB-43420)

Exploit prediction

91.30% chance of exploitation in the next 30 days, higher than 99.8% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • EDB-43420 WordPress Plugin Smart Google Code Inserter < 3.5 - Authentication Bypass / SQL Injection webapps, 2018-01-03
  • Nuclei template Oturia WordPress Smart Google Code Inserter <3.5 - Authentication Bypass nuclei detection template
  • limbenjamin.com https://limbenjamin.com/articles/smart-google-code-inserter-auth-bypass.html referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.0 9.8 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P

Classification

Weakness
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.