Strategic Overview
- Status
- Patched in 3.7.28
- Affected Core
- WordPress 5.0
- Affected Version
3.7 – 5.0 · 15 branches- CVSS
- 7.7High
- Weakness type
- CWE-285 · Improper Authorization
- CVE
CVE-2018-20147
At a glance
CVE-2018-20147 is a high-severity Improper Authorization vulnerability in the WordPress 5.0 WordPress release line, affecting 3.7 – 5.0 · 15 branches. It carries a CVSS score of 7.7 (reachable over the network; low attack complexity; high availability impact). The issue is fixed in version 3.7.28; sites on affected versions should update now. Disclosed December 2018, reported by Karim El Ouerghemmi.
Vulnerability Overview
In WordPress before 4.9.9 and 5.x before 5.0.1, authors could modify metadata to bypass intended restrictions on deleting files.
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 interaction from a victim user. A successful exploit has high impact on availability.
CWE-285: Improper Authorization
Reaching this weakness in WordPress 5.0 3.7 – 5.0 · 15 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 5.0 the fix is 3.7.28: builds 3.7 – 5.0 · 15 branches are affected, anything from 3.7.28 onward is not.
Remediation
Update to one of the following versions, or a newer patched version: 3.7.28, 3.8.28, 3.9.26, 4.0.25, 4.1.25, 4.2.22, 4.3.18, 4.4.17, 4.5.16, 4.6.13, 4.7.12, 4.8.8, 4.9.9, 5.0.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.28 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 - 8.3CVE-2017-5491: WordPress Core < 4.7.1 Authorization Bypass
CVE-2017-5491 - 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 5.0
- 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