CVE-2018-3811 in the critical feed json
SQL Injection vulnerability in the Oturia Smart Google Code Inserter plugin before 3.5 for WordPress allows unauthenticated attackers to ex…
published 8y ago modified 4mo ago also EUVD-2018-15600
- cvss
- 9.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 42.3%
- EPSS 42.3% chance of exploitation in 30 days, percentile 98%
- public exploits
- 1
- Exploit-DB
Summary
SQL Injection vulnerability in the Oturia Smart Google Code Inserter plugin before 3.5 for WordPress allows unauthenticated attackers to execute SQL queries in the context of the web server. The saveGoogleAdWords() function in smartgooglecode.php did not use prepared statements and did not sanitize the $_POST["oId"] variable before passing it as input into the SQL query.
Patch / fix
- oturia smart_google_code_inserter 3.5
Is CVE-2018-3811 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 FencerTimeline
- Published
- First public exploit (EDB-43420)
Exploit prediction
42.28% chance of exploitation in the next 30 days, higher than 98% 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
- 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
-
- CWE-89 Improper Neutralization of Special Elements used in an SQL Command
- Technology feeds
References
-
exploit-db.com
/exploits/43420/
exploit, third-party-advisory, vdb-entry
-
limbenjamin.com
/articles/smart-google-code-inserter-auth-bypass.html
exploit, third-party-advisory
-
wpvulndb.com
/vulnerabilities/8988
third-party-advisory, vdb-entry
-
wordpress.org
/plugins/smart-google-code-inserter/#developers
release-notes, third-party-advisory
Sources
- CVE List CVE-2018-3811
- NVD CVE-2018-3811
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.