IP Blacklist Cloud < 3.41 - SQL Injections
Strategic Overview
- Status
- Patched in 3.41
- Affected Plugin
- IP Blacklist Cloud
- Affected Version
< 3.41- 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 IP Blacklist Cloud WordPress plugin, affecting versions < 3.41. 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.41; sites on affected versions should update now. Disclosed February 2015, reported by Mika Epstein.
Vulnerability Overview
The IP Blacklist Cloud plugin for WordPress is vulnerable to SQL Injections via several parameters in versions before 3.41 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL queries. This makes it possible for 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 IP Blacklist Cloud < 3.41 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 IP Blacklist Cloud the fix is 3.41: builds < 3.41 are affected, anything from 3.41 onward is not.
Remediation
Update to version 3.41, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to IP Blacklist Cloud: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: IP Blacklist Cloud 3.41 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in IP Blacklist Cloud
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C