CVE-2015-5731

WordPress Core < 4.2.4 - Cross-Site Request Forgery to Post Lockage

2015-08-04 00:00
Mohamed A. Baset

Strategic Overview

Status
Patched in 3.7.10
Affected Core
WordPress 4.2
Affected Version
3.7 – 4.2.3 · 7 branches
CVSS
9.6Critical
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2015-5731
View all WordPress 4.2 vulnerabilities

At a glance

CVE-2015-5731 is a critical-severity Cross-Site Request Forgery (CSRF) vulnerability in the WordPress 4.2 WordPress release line, affecting 3.7 – 4.2.3 · 7 branches. It carries a CVSS score of 9.6 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 3.7.10; sites on affected versions should update now. Disclosed August 2015, reported by Mohamed A. Baset.

Vulnerability Overview

Cross-site request forgery (CSRF) vulnerability in wp-admin/post.php in WordPress before 4.2.4 allows remote attackers to hijack the authentication of administrators for requests that lock a post, and consequently cause a denial of service (editing blockage), via a get-post-lock action.

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. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

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

Reaching this weakness in WordPress 4.2 3.7 – 4.2.3 · 7 branches 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 4.2 the fix is 3.7.10: builds 3.7 – 4.2.3 · 7 branches are affected, anything from 3.7.10 onward is not.

Remediation

Update to one of the following versions, or a newer patched version: 3.7.10, 3.8.10, 3.9.8, 4.0.7, 4.1.7, 4.2.4

How does WordSec protect against this?

The attempt arrives as an ordinary request to WordPress 4.2: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: updating to 3.7.10 is the step that ends it.

  • Firewall
  • Alerts

External References

Related records

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