CVE-2011-0760

WP Related Posts <= 1.0 - Cross-Site Request Forgery

2011-03-17 00:00
Gabriel Quadros

Strategic Overview

Status
Patched in 1.1
Affected Plugin
WP Related Posts
Affected Version
< 1.1
CVSS
7.1High
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2011-0760
View all WP Related Posts vulnerabilities

At a glance

CVE-2011-0760 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the WP Related Posts WordPress plugin, affecting versions < 1.1. It carries a CVSS score of 7.1 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.1; sites on affected versions should update now. Disclosed March 2011, reported by Gabriel Quadros.

Vulnerability Overview

Multiple cross-site request forgery (CSRF) vulnerabilities in the configuration screen in wp-relatedposts.php in the WP Related Posts plugin 1.0 for WordPress allow remote attackers to hijack the authentication of administrators for requests that insert cross-site scripting (XSS) sequences via the (1) wp_relatedposts_title, (2) wp_relatedposts_num, or (3) wp_relatedposts_type parameter.

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 privileges on the target site.

CWE-352: Cross-Site Request Forgery (CSRF)

Reaching this weakness in WP Related Posts < 1.1 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For WP Related Posts the fix is 1.1: builds < 1.1 are affected, anything from 1.1 onward is not.

Remediation

Update to version 1.1, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to WP Related Posts: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WP Related Posts 1.1 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C