WordPress Core < 4.2.4 - Cross-Site Request Forgery to Post Lockage
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
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
Same weakness class
- 9.6CVE-2019-9787: WordPress Core < 5.1.1 CSRF to Cross-Site Scripting
CVE-2019-9787 - 8.8WordPress Core < 6.0.3 Cross-Site Request Forgery via wp-trackback.php
- 8.8CVE-2017-9064: WordPress Core CSRF Filesystem Credential Update
CVE-2017-9064 - 8.8CVE-2017-6819: WordPress Core < 4.7.3 Cross-Site Request Forgery
CVE-2017-6819
Other vulnerabilities in WordPress 4.2
- 9.8CVE-2026-63030: WordPress Core 6.9 - 7.0.1 Remote Code Execution
CVE-2026-63030 - 9.8CVE-2024-31211: WordPress Core 6.4.0 - 6.4.1 RCE POP Chain
CVE-2024-31211 - 9.8WordPress Core < 6.0.3 SQL Injection via WP_Date_Query
- 9.8CVE-2021-29476: WordPress Core < 5.5.3 PHP Object Injection Gadget
CVE-2021-29476 - 9.8CVE-2017-16510: WordPress Core SQL Injection
CVE-2017-16510 - 9.8CVE-2017-14723: WordPress Core < 4.8.2 SQL Injection
CVE-2017-14723 - 9.8CVE-2007-6013: WordPress Core 1.5 - 2.3.1 Authorization Bypass
CVE-2007-6013 - 9.8CVE-2007-6318: WordPress Core < 2.3.2 SQL Injection
CVE-2007-6318
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C