CVE-2020-11028: Unauthenticated disclosure of certain private posts in WordPress
Vendor fix available · Affected: WordPress · Exploitation: possible (1 to 10%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 83% of scored CVEs
DescriptionCVE.org
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).
Affected products1
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- WordPress · WordPress>= 5.4.0, < 5.4.1; >= 5.3.0, < 5.3.3; >= 5.2.0, < 5.2.6; >= 5.1.0, < 5.1.5; >= 5.0.0, < 5.0.9; >= 4.9.0, < 4.9.14 and 12 more
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Possible (1 to 10%). EPSS between 1% and 10%.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Vendor
- WordPress
- Published
- April 2020
CoverageNo articles yet
No CyberSIXT article names CVE-2020-11028 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.