WordPress Zero Spam <= 2.1.1 - SQL Injection
Strategic Overview
- Status
- Patched in 2.2.0
- Affected Plugin
- Zero Spam for WordPress
- Affected Version
<= 2.1.1- CVSS
- 9.8Critical
- Weakness type
- CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
- CVE
CVE pending
At a glance
This record tracks a critical-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the Zero Spam for WordPress WordPress plugin, affecting versions <= 2.1.1. 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 2.2.0; sites on affected versions should update now. Disclosed August 2016, reported by thiagolcks.
Vulnerability Overview
The WordPress Zero Spam plugin for WordPress is vulnerable to Blind SQL Injection in versions up to, and including, 2.1.1 due to insufficient escaping on the user supplied Client-IP header parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.
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')
Reaching this weakness in Zero Spam for WordPress <= 2.1.1 takes a caller who can reach the endpoint. 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 Zero Spam for WordPress the fix is 2.2.0: builds <= 2.1.1 are affected, anything from 2.2.0 onward is not.
Remediation
Update to version 2.2.0, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Zero Spam for WordPress: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Zero Spam for WordPress 2.2.0 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in Zero Spam for WordPress
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C