CVE-2020-28039 in the critical feed json
is_protected_meta in wp-includes/meta.php in WordPress before 5.5.2 allows arbitrary file deletion because it does not properly determine w…
published 6y ago modified 2mo ago also BIT-wordpress-2020-28039 , BIT-wordpress-multisite-2020-28039 , EUVD-2020-20530
- cvss
- 9.1
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 4.1%
- EPSS 4.1% chance of exploitation in 30 days, percentile 90%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- bitnami wordpress 5.5.2
- bitnami wordpress-multisite 5.5.2
- wordpress wordpress 5.5.2
- wordpress Debian 14, Debian 13, Debian 12 5.5.3+dfsg1-1
debian advisories DEBIAN-CVE-2020-28039
- wordpress Arch Linux 5.5.3-1
arch linux advisories AVG-1257
Is CVE-2020-28039 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2020-28039 updated cvss 9.1
wordpress: protected meta that could lead to arbitrary file deletion
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
4.11% chance of exploitation in the next 30 days, higher than 90% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 9.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H |
| NVD | 2.0 | 6.4 | AV:N/AC:L/Au:N/C:N/I:P/A:P |
| OSV | 3.1 | 9.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| bitnami | wordpress | <5.5.2 |
5.5.2 |
| bitnami | wordpress-multisite | <5.5.2 |
5.5.2 |
Classification
- Technology feeds
References
-
github.com
/WordPress/wordpress-develop/commit/d5ddd6d4be1bc9fd16b7796842e6fb26315705ad
patch, third-party-advisory, advisory
-
debian.org
/security/2020/dsa-4784
vendor-advisory, third-party-advisory, advisory
-
lists.fedoraproject.org
/archives/list/package-announce%40lists.fedoraproject.org/message/VAVVYJKA2I6CRQUINECDPBGWMQDEG244/
vendor-advisory, web
-
lists.fedoraproject.org
/archives/list/package-announce%40lists.fedoraproject.org/message/VUXVUAKL2HL4QYJEPHBNVQQWRMFMII2Y/
vendor-advisory, web
-
lists.fedoraproject.org
/archives/list/package-announce%40lists.fedoraproject.org/message/CHHVNK2WYAM3ZTCXTFSEIT56IKLVJHU3/
vendor-advisory, web
-
wordpress.org
/news/2020/10/wordpress-5-5-2-security-and-maintenance-release/
release-notes, vendor-advisory, advisory
-
wpscan.com
/vulnerability/10452
third-party-advisory, advisory
-
lists.debian.org
/debian-lts-announce/2020/11/msg00004.html
mailing-list, third-party-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2020-28039
web
Sources
- CVE List CVE-2020-28039
- NVD CVE-2020-28039
- OSV BIT-wordpress-2020-28039
- OSV BIT-wordpress-multisite-2020-28039
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.