CVE-2013-3476

Related Posts < 2.7.2 - Cross-Site Request Forgery

2014-08-01 00:00
Charlie Eriksen

Strategic Overview

Status
Patched in 2.7.2
Affected Version
< 2.7.2
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2013-3476
View all WordPress Related Posts vulnerabilities

At a glance

CVE-2013-3476 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the WordPress Related Posts WordPress plugin, affecting versions < 2.7.2. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.7.2; sites on affected versions should update now. Disclosed August 2014, reported by Charlie Eriksen.

Vulnerability Overview

Cross-site request forgery (CSRF) vulnerability in the WordPress Related Posts plugin before 2.7.2 for WordPress allows remote attackers to hijack the authentication of users for requests that change settings via unspecified vectors.

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 WordPress Related Posts < 2.7.2 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 WordPress Related Posts the fix is 2.7.2: builds < 2.7.2 are affected, anything from 2.7.2 onward is not.

Remediation

Update to version 2.7.2, or a newer patched version

How does WordSec protect against this?

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

  • Firewall
  • Alerts

External References

Related records

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