Strategic Overview
- Status
- Patched in 1.62
- Affected Plugin
- WP-PostRatings
- Affected Version
<= 1.61- CVSS
- 8.8High
- Weakness type
- CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
- CVE
CVE-2011-4646
At a glance
CVE-2011-4646 is a high-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the WP-PostRatings WordPress plugin, affecting versions <= 1.61. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). The issue is fixed in version 1.62; sites on affected versions should update now. Disclosed October 2011.
Vulnerability Overview
SQL injection vulnerability in wp-postratings.php in the WP-PostRatings plugin 1.50, 1.61, and probably other versions before 1.62 for WordPress allows remote authenticated users with the Author role to execute arbitrary SQL commands via the id attribute of the ratings shortcode when creating a post. NOTE: some of these details are obtained 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 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-PostRatings <= 1.61 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-PostRatings the fix is 1.62: builds <= 1.61 are affected, anything from 1.62 onward is not.
Remediation
Update to version 1.62, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to WP-PostRatings: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WP-PostRatings 1.62 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in WP-PostRatings
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C