Strategic Overview
- Status
- Patched in 1.2
- Affected Plugin
- Pay With Tweet
- Affected Version
<= 1.1- CVSS
- 8.8High
- Weakness type
- CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
- CVE
CVE-2012-5350
At a glance
CVE-2012-5350 is a high-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the Pay With Tweet WordPress plugin, affecting versions <= 1.1. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account. The issue is fixed in version 1.2; sites on affected versions should update now. Disclosed January 2012, reported by Gianluca Brindisi.
Vulnerability Overview
SQL injection vulnerability in the Pay With Tweet plugin before 1.2 for WordPress allows remote authenticated users with certain permissions to execute arbitrary SQL commands via the id parameter in a paywithtweet shortcode.
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 Pay With Tweet <= 1.1 takes any authenticated account. 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 Pay With Tweet the fix is 1.2: builds <= 1.1 are affected, anything from 1.2 onward is not.
Remediation
Update to version 1.2, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Pay With Tweet: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Pay With Tweet 1.2 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in Pay With Tweet
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C