Strategic Overview
- Status
- Patched in 2.1
- Affected Plugin
- WP-RecentComments
- Affected Version
<= 2.0.7- CVSS
- 9.8Critical
- Weakness type
- CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
- CVE
CVE-2012-1067
At a glance
CVE-2012-1067 is a critical-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the WP-RecentComments WordPress plugin, affecting versions <= 2.0.7. 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.1; sites on affected versions should update now. Disclosed September 2011.
Vulnerability Overview
SQL injection vulnerability in the WP-RecentComments plugin 2.0.7 for WordPress allows remote attackers to execute arbitrary SQL commands via the id parameter in an rc-content action to index.php. NOTE: the provenance of this information is unknown; the details are obtained solely from third party information.
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 WP-RecentComments <= 2.0.7 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 WP-RecentComments the fix is 2.1: builds <= 2.0.7 are affected, anything from 2.1 onward is not.
Remediation
Update to version 2.1, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to WP-RecentComments: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WP-RecentComments 2.1 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in WP-RecentComments
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C