Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1894982 (CVE-2020-28039) - CVE-2020-28039 wordpress: protected meta that could lead to arbitrary file deletion
Summary: CVE-2020-28039 wordpress: protected meta that could lead to arbitrary file de...
Keywords:
Status: CLOSED UPSTREAM
Alias: CVE-2020-28039
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1894983 1894984
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-11-05 14:18 UTC by Guilherme de Almeida Suckevicz
Modified: 2020-11-05 14:21 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-11-05 14:21:30 UTC
Embargoed:


Attachments (Terms of Use)

Description Guilherme de Almeida Suckevicz 2020-11-05 14:18:39 UTC
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.

References:
https://wordpress.org/news/2020/10/wordpress-5-5-2-security-and-maintenance-release/
https://wpscan.com/vulnerability/10452

Upstream patch:
https://github.com/WordPress/wordpress-develop/commit/d5ddd6d4be1bc9fd16b7796842e6fb26315705ad

Comment 1 Guilherme de Almeida Suckevicz 2020-11-05 14:18:58 UTC
Created wordpress tracking bugs for this issue:

Affects: epel-all [bug 1894984]
Affects: fedora-all [bug 1894983]

Comment 2 Product Security DevOps Team 2020-11-05 14:21:30 UTC
This CVE Bugzilla entry is for community support informational purposes only as it does not affect a package in a commercially supported Red Hat product. Refer to the dependent bugs for status of those individual community products.


Note You need to log in before you can comment on or make changes to this bug.