CVE-2018-3811

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2022-05-14. NVD baseline CVSS 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Weaponized
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 43%CVSS: 9.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
9.8
EG Score
9.8(medium)
EPSS
98.6%
KEV
Not listed

Published

January 1, 2018

Last Modified

November 21, 2024

Advisory Details (3)

Auto-updated May 23, 2026
🔬 Proof of concept available. No patch confirmed yet.
generic🟡 PoC Available

WordPress Plugin Smart Google Code Inserter < 3.5 - Authentication Bypass / SQL Injection - PHP webapps Exploit

https://www.exploit-db.com/exploits/43420/
generic

Smart Google Code Inserter – WordPress plugin | WordPress.org

https://wordpress.org/plugins/smart-google-code-inserter/#developers
generic🟡 PoC Available

Smart Google Code Inserter < 3.5 - Auth Bypass/SQLi

https://limbenjamin.com/articles/smart-google-code-inserter-auth-bypass.html

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 40× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-06 16:24 UTCEPSS rescore
  2. 2026-07-06 16:24 UTCEPSS rescore
  3. 2026-07-05 02:27 UTCEPSS rescore
  4. 2026-07-02 16:54 UTCEPSS rescore
  5. 2026-07-01 15:03 UTCEPSS rescore
  6. 2026-07-01 15:03 UTCEPSS rescore
  7. 2026-06-30 23:20 UTCEPSS rescore
  8. 2026-06-30 23:19 UTCEPSS rescore
  9. 2026-06-28 14:04 UTCEPSS rescore
  10. 2026-06-28 04:53 UTCEPSS rescore
  11. 2026-06-28 04:53 UTCEPSS rescore
  12. 2026-06-27 03:06 UTCEPSS rescore
  13. 2026-06-27 03:06 UTCEPSS rescore
  14. 2026-06-25 13:47 UTCEPSS rescore
  15. 2026-06-25 13:47 UTCEPSS rescore
  16. 2026-06-23 21:30 UTCEPSS rescore
  17. 2026-06-23 21:30 UTCEPSS rescore
  18. 2026-06-23 21:30 UTCEPSS rescore
  19. 2026-06-22 14:23 UTCEPSS rescore
  20. 2026-06-21 01:57 UTCEPSS rescore
  21. 2026-06-21 01:57 UTCEPSS rescore
  22. 2026-06-19 19:23 UTCEPSS rescore
  23. 2026-06-19 19:23 UTCEPSS rescore
  24. 2026-06-18 17:50 UTCEPSS rescore
  25. 2026-06-18 17:50 UTCEPSS rescore
Show 35 more
  1. 2026-06-17 17:50 UTCEPSS rescore
  2. 2026-06-17 17:50 UTCEPSS rescore
  3. 2026-06-16 17:50 UTCEPSS rescore
  4. 2026-06-16 17:50 UTCEPSS rescore
  5. 2026-06-15 17:45 UTCEPSS rescore
  6. 2026-06-14 23:15 UTCEPSS rescore
  7. 2026-06-14 23:14 UTCEPSS rescore
  8. 2026-06-13 22:58 UTCEPSS rescore
  9. 2026-06-12 23:09 UTCEPSS rescore
  10. 2026-06-12 23:09 UTCEPSS rescore
  11. 2026-06-11 13:57 UTCEPSS rescore
  12. 2026-06-10 22:16 UTCEPSS rescore
  13. 2026-06-10 13:19 UTCEPSS rescore
  14. 2026-06-08 14:14 UTCEPSS rescore
  15. 2026-06-08 14:14 UTCEPSS rescore
  16. 2026-06-06 13:45 UTCEPSS rescore
  17. 2026-06-06 13:45 UTCEPSS rescore
  18. 2026-06-05 22:45 UTCEPSS rescore
  19. 2026-06-05 22:45 UTCEPSS rescore
  20. 2026-06-05 06:08 UTCEPSS rescore
  21. 2026-06-05 06:08 UTCEPSS rescore
  22. 2026-06-04 13:10 UTCEPSS rescore
  23. 2026-06-02 20:11 UTCEPSS rescore
  24. 2026-06-02 20:11 UTCEPSS rescore
  25. 2026-05-31 22:29 UTCEPSS rescore
  26. 2026-05-29 13:41 UTCEPSS rescore
  27. 2026-05-28 13:42 UTCEPSS rescore
  28. 2026-05-28 13:42 UTCEPSS rescore
  29. 2026-05-28 13:00 UTCEG score recompute
  30. 2026-05-28 13:00 UTCGHSA enrichment
  31. 2026-05-27 13:38 UTCEPSS rescore
  32. 2026-05-27 13:38 UTCEPSS rescore
  33. 2026-05-26 13:42 UTCEPSS rescore
  34. 2026-05-26 13:42 UTCEPSS rescore
  35. 2026-05-25 02:09 UTCOSV refresh

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-43420✓ verified
    First seen Jan 3, 2018

    WordPress Plugin Smart Google Code Inserter < 3.5 - Authentication Bypass / SQL Injection

    Open source ↗

Frequently asked(5)

What is CVE-2018-3811?
CVE-2018-3811 is a critical vulnerability published on January 1, 2018. 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…
When was CVE-2018-3811 disclosed?
CVE-2018-3811 was first published in the National Vulnerability Database on January 1, 2018, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2018-3811 actively exploited?
CVE-2018-3811 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 98.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2018-3811?
CVE-2018-3811 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2018-3811?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2018-3811, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2018-3811

Explore →

Is Your Infrastructure Affected by CVE-2018-3811?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.