Strategic Overview
- Status
- Patched in 3.7.17
- Affected Core
- WordPress 4.7
- Affected Version
3.7 – 4.7.0 · 12 branches- CVSS
- 8.3High
- Weakness type
- CWE-285 · Improper Authorization
- CVE
CVE-2017-5491
At a glance
CVE-2017-5491 is a high-severity Improper Authorization vulnerability in the WordPress 4.7 WordPress release line, affecting 3.7 – 4.7.0 · 12 branches. It carries a CVSS score of 8.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 3.7.17; sites on affected versions should update now. Disclosed January 2017, reported by John Blackbourn.
Vulnerability Overview
wp-mail.php in WordPress before 4.7.1 might allow remote attackers to bypass intended posting restrictions via a spoofed mail server with the mail.example.com name.
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, and no interaction from a victim user.
CWE-285: Improper Authorization
Reaching this weakness in WordPress 4.7 3.7 – 4.7.0 · 12 branches takes a caller who can reach the endpoint. Improper authorization means a permission check exists but does not cover the case being exercised, so a caller who is allowed to do one thing is allowed to do a neighbouring thing as well.
A lower-privileged account performs an action reserved for a higher one, which on a multi-author or membership site means an ordinary user reaching administrative behaviour. For WordPress 4.7 the fix is 3.7.17: builds 3.7 – 4.7.0 · 12 branches are affected, anything from 3.7.17 onward is not.
Remediation
Update to one of the following versions, or a newer patched version: 3.7.17, 3.8.17, 3.9.15, 4.0.14, 4.1.14, 4.2.11, 4.3.7, 4.4.6, 4.5.5, 4.6.2, 4.7.1
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: updating to 3.7.17 is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
- 9.8CVE-2006-4028: WordPress Core < 2.0.4 Privilege Escalation
CVE-2006-4028 - 7.7CVE-2018-20147: WordPress Core < 5.0.1 Arbitrary File Deletion
CVE-2018-20147 - 7.3CVE-2017-1001000: WordPress Core < 4.7.2 Arbitrary Page Modification
CVE-2017-1001000 - 6.3CVE-2017-9062: WordPress Core < 4.7.5 Mishandling Post Meta Values
CVE-2017-9062
Other vulnerabilities in WordPress 4.7
- 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