Wp Recentcomments: Cross-site scripting
Wp Recentcomments is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
- Component
- Wp Recentcomments
- Plugin slug
wp-recentcomments- Affected
- See vendor advisory
- Safe version
- See mitigation notes
- Published
- Feb 14, 2012
This CVE was published Feb 14, 2012 and is one of 3 known issues for this plugin.
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.
Technical description
Cross-site scripting (XSS) vulnerability in the rc_ajax function in core.php in the WP-RecentComments plugin before 2.0.7 for WordPress allows remote attackers to inject arbitrary web script or HTML via the page parameter, related to AJAX paging.
NVD vector: AV:N/AC:M/Au:N/C:N/I:P/A:N
Primary and upstream sources
- NVD record for CVE-2012-1068
- WordPress upstream reference plugins.trac.wordpress.org
- Upstream reference secunia.com
- WordPress.org plugin page wordpress.org
- Upstream reference osvdb.org
- Upstream reference securityfocus.com
- Upstream reference exchange.xforce.ibmcloud.com
- WordPress upstream reference plugins.trac.wordpress.org
- Upstream reference secunia.com
- WordPress.org plugin page wordpress.org
- Upstream reference osvdb.org
- Upstream reference securityfocus.com
- Upstream reference exchange.xforce.ibmcloud.com