Pay With Tweet: SQL injection
Pay With Tweet is affected by SQL injection. Exposure depends on how the affected operation is made reachable by the site. A successful request can alter database queries and expose or modify WordPress data.
- Component
- Pay With Tweet
- Plugin slug
pay-with-tweet- Affected
- See vendor advisory
- Safe version
- See mitigation notes
- Published
- Oct 09, 2012
This CVE was published Oct 09, 2012 and is one of 2 known issues for this plugin.
Update, patch or deactivate.
Update Pay With Tweet to a release outside the affected range, or disable and remove it until a fixed version is available.
No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.
Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.
Technical description
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.
NVD vector: AV:N/AC:M/Au:S/C:P/I:P/A:P
Primary and upstream sources
- NVD record for CVE-2012-5350
- Upstream reference secunia.com
- WordPress.org plugin page wordpress.org
- Upstream reference exploit-db.com
- Upstream reference osvdb.org
- Upstream reference securityfocus.com
- Upstream reference exchange.xforce.ibmcloud.com
- Upstream reference secunia.com
- WordPress.org plugin page wordpress.org
- Upstream reference exploit-db.com
- Upstream reference osvdb.org
- Upstream reference securityfocus.com
- Upstream reference exchange.xforce.ibmcloud.com