WordPress up to 5.5.1 File wp-includes/meta.php is_protected_meta path traversal
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.5 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, has been found in WordPress up to 5.5.1. The impacted element is the function is_protected_meta of the file wp-includes/meta.php of the component File Handler. Performing a manipulation results in path traversal.
This vulnerability was named CVE-2020-28039. There is no available exploit.
It is advisable to upgrade the affected component.
Details
A vulnerability was found in WordPress up to 5.5.1 (Content Management System). It has been classified as problematic. This affects the function is_protected_meta of the file wp-includes/meta.php of the component File Handler. The manipulation with an unknown input leads to a path traversal vulnerability. CWE is classifying the issue as CWE-22. The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. This is going to have an impact on integrity, and availability.
The weakness was presented 11/03/2020. The advisory is shared at wpscan.com. This vulnerability is uniquely identified as CVE-2020-28039. The exploitability is told to be easy. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1006 for this issue.
By approaching the search of inurl:wp-includes/meta.php it is possible to find vulnerable targets with Google Hacking.
Upgrading to version 5.5.2 eliminates this vulnerability. Applying a patch is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Name
Version
License
Website
- Product: https://wordpress.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.8VulDB Meta Temp Score: 6.7
VulDB Base Score: 4.6
VulDB Temp Score: 4.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.1
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Path traversalCWE: CWE-22
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
Google Hack: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: WordPress 5.5.2
Patch: github.com
Timeline
10/31/2020 🔍11/03/2020 🔍
11/03/2020 🔍
12/01/2020 🔍
Sources
Product: wordpress.comAdvisory: wpscan.com
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2020-28039 (🔍)
GCVE (CVE): GCVE-0-2020-28039
GCVE (VulDB): GCVE-100-164193
Entry
Created: 11/03/2020 08:47Updated: 12/01/2020 11:47
Changes: 11/03/2020 08:47 (42), 12/01/2020 11:45 (2), 12/01/2020 11:47 (18)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.