WordPress security changelog
HIGH CVE-2012-1067 Modified

Wp Recentcomments: SQL injection

Wp Recentcomments 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.

CVE / CNA score 7.5 CVSS · cve@mitre.org
NVD score 7.5 CVSS 2.0 · nvd@nist.gov
Component
Wp Recentcomments
Plugin slug
wp-recentcomments
Affected
See vendor advisory
Safe version
See mitigation notes
Published
Feb 14, 2012
Weakness
CWE-89 — Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

This CVE was published Feb 14, 2012 and is one of 3 known issues for this plugin.

What to do

Update, patch or deactivate.

Update Wp Recentcomments 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.

Source record

Technical description

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.

NVD vector: AV:N/AC:L/Au:N/C:P/I:P/A:P

References

Primary and upstream sources