| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.0 | $0-$5k | 0.00 |
Summary
A vulnerability labeled as problematic has been found in WordPress. This affects an unknown part of the component Private Post Handler. Such manipulation leads to access control. This vulnerability is referenced as CVE-2020-11028. It is possible to launch the attack remotely. No exploit is available. The affected component should be upgraded.
Details
A vulnerability, which was classified as problematic, has been found in WordPress (Content Management System). Affected by this issue is an unknown part of the component Private Post Handler. The manipulation with an unknown input leads to a access control vulnerability. Using CWE to declare the problem leads to CWE-284. The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. Impacted is confidentiality. CVE summarizes:
In affected versions of WordPress, some private posts, which were previously public, can result in unauthenticated disclosure under a specific set of conditions. This has been patched in version 5.4.1, along with all the previously affected versions via a minor release (5.3.3, 5.2.6, 5.1.5, 5.0.9, 4.9.14, 4.8.13, 4.7.17, 4.6.18, 4.5.21, 4.4.22, 4.3.23, 4.2.27, 4.1.30, 4.0.30, 3.9.31, 3.8.33, 3.7.33).
The weakness was published 04/30/2020 (GitHub Repository). The advisory is shared for download at github.com. This vulnerability is handled as CVE-2020-11028 since 03/30/2020. The exploitation is known to be difficult. The attack may be launched remotely. No form of authentication is required for exploitation. Successful exploitation requires user interaction by the victim. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1068.
Upgrading to version 5.4.1 eliminates this vulnerability.
Similar entries are available at VDB-154642, VDB-154641, VDB-154639 and VDB-154638. VulDB is the best source for vulnerability data and more expert information about this specific topic.
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: 5.0VulDB Meta Temp Score: 5.0
VulDB Base Score: 3.4
VulDB Temp Score: 3.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.8
NVD Vector: 🔍
CNA Base Score: 5.8
CNA Vector (GitHub, Inc.): 🔍
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: Access controlCWE: CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
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.4.1
Timeline
03/30/2020 🔍04/30/2020 🔍
05/01/2020 🔍
05/06/2025 🔍
Sources
Product: wordpress.comAdvisory: GHSA-xhx9-759f-6p2w
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2020-11028 (🔍)
GCVE (CVE): GCVE-0-2020-11028
GCVE (VulDB): GCVE-100-154640
See also: 🔍
Entry
Created: 05/01/2020 08:55Updated: 05/06/2025 04:35
Changes: 05/01/2020 08:55 (39), 05/01/2020 09:00 (12), 10/14/2020 16:09 (1), 10/14/2020 16:12 (1), 06/04/2024 18:14 (17), 06/04/2024 18:21 (19), 05/06/2025 04:35 (8)
Complete: 🔍
Cache ID: 216::103
VulDB is the best source for vulnerability data and more expert information about this specific topic.
No comments yet. Languages: en.
Please log in to comment.