CVE-2020-28039
CRITICALCVSS 9.1/10EPSS 4.06%
Last modified
CVE-2020-28039 is a critical-severity vulnerability rated 9.1/10 on the CVSS scale. is_protected_meta in wp-includes/meta.php in WordPress before 5.5.2 allows arbitrary file deletion because it does not properly determine whether a meta key is considered protected.. EPSS estimates a 4.06% chance of exploitation in the next 30 days.
Description
is_protected_meta in wp-includes/meta.php in WordPress before 5.5.2 allows arbitrary file deletion because it does not properly determine whether a meta key is considered protected.
Metrics
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Wordpress | Wordpress | < 5.5.2 |
| Debian | Debian Linux | 9.0 |
| Debian | Debian Linux | 10.0 |
| Canonical | Ubuntu Linux | 16.04 |
| Canonical | Ubuntu Linux | 18.04 |
| Canonical | Ubuntu Linux | 20.04 |
References
- https://github.com/WordPress/wordpress-develop/commit/d5ddd6d4be1bc9fd16b7796842e6fb26315705adPatch, Third Party Advisory
- https://lists.debian.org/debian-lts-announce/2020/11/msg00004.htmlMailing List, Third Party Advisory
- https://wordpress.org/news/2020/10/wordpress-5-5-2-security-and-maintenance-release/Release Notes, Vendor Advisory
- https://wpscan.com/vulnerability/10452Third Party Advisory
- https://www.debian.org/security/2020/dsa-4784Third Party Advisory
- https://github.com/WordPress/wordpress-develop/commit/d5ddd6d4be1bc9fd16b7796842e6fb26315705adPatch, Third Party Advisory
- https://lists.debian.org/debian-lts-announce/2020/11/msg00004.htmlMailing List, Third Party Advisory
- https://wordpress.org/news/2020/10/wordpress-5-5-2-security-and-maintenance-release/Release Notes, Vendor Advisory
- https://wpscan.com/vulnerability/10452Third Party Advisory
- https://www.debian.org/security/2020/dsa-4784Third Party Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2020-28039?
is_protected_meta in wp-includes/meta.php in WordPress before 5.5.2 allows arbitrary file deletion because it does not properly determine whether a meta key is considered protected.
How severe is CVE-2020-28039?
CVE-2020-28039 has a CVSS score of 9.1/10 (CRITICAL severity). The EPSS model estimates a 4.06% probability of exploitation in the next 30 days.
How do I fix CVE-2020-28039?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2020
- CVE-2020-28033WordPress before 5.5.2 mishandles embeds from disabled sites…7.5
- CVE-2020-28034WordPress before 5.5.2 allows XSS associated with global var…6.1
- CVE-2020-28035WordPress before 5.5.2 allows attackers to gain privileges v…9.8
- CVE-2020-28036wp-includes/class-wp-xmlrpc-server.php in WordPress before 5…9.8
- CVE-2020-28037is_blog_installed in wp-includes/functions.php in WordPress …9.8
- CVE-2020-28038WordPress before 5.5.2 allows stored XSS via post slugs.6.1
- CVE-2020-2804Vulnerability in the MySQL Server product of Oracle MySQL (c…5.9
- CVE-2020-28040WordPress before 5.5.2 allows CSRF attacks that change a the…4.3
- CVE-2020-28041The SIP ALG implementation on NETGEAR Nighthawk R7000 1.0.9.…6.5
- CVE-2020-28042ServiceStack before 5.9.2 mishandles JWT signature verificat…5.3
- CVE-2020-28043MISP through 2.4.133 allows SSRF in the REST client via the …7.5
- CVE-2020-28044An attacker with physical access to a PAX Point Of Sale devi…6.8
Are you affected by CVE-2020-28039?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
