Smart Google Code Inserter < 3.5 - Unauthenticated SQL Injection
Strategic Overview
- Status
- Patched in 3.5
- Affected Plugin
- Smart Google Code Inserter
- Affected Version
< 3.5- CVSS
- 9.8Critical
- Weakness type
- CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
- CVE
CVE-2018-3811
At a glance
CVE-2018-3811 is a critical-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the Smart Google Code Inserter WordPress plugin, affecting versions < 3.5. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 3.5; sites on affected versions should update now. Disclosed January 2018, reported by Benjamin Lim.
Vulnerability Overview
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.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Smart Google Code Inserter < 3.5 carries this weakness at oId, and reaching it takes no account at all. SQL injection happens when request data is concatenated into a query instead of being bound as a parameter, letting an attacker change the structure of the statement rather than just its values.
A working injection can read any table the database user can see, which on a WordPress install means user records, password hashes and session or API secrets stored in options. For Smart Google Code Inserter the fix is 3.5: builds < 3.5 are affected, anything from 3.5 onward is not.
Remediation
Update to version 3.5, or a newer patched version
How does WordSec protect against this?
Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Smart Google Code Inserter 3.5 closes this, and updating the plugin is the step that ends it.
- Firewall
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in Smart Google Code Inserter
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C