Unauthenticated disclosure of certain private posts in WordPress
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.4.1, 5.3.3, 5.2.6, 5.1.5, 5.0.9, and 13 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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).
Timeline
- CVE published
- Record last updated
Affected versions
- WordPress WordPress
From 5.4.0 · fixed in 5.4.1; From 5.3.0 · fixed in 5.3.3; From 5.2.0 · fixed in 5.2.6; From 5.1.0 · fixed in 5.1.5; From 5.0.0 · fixed in 5.0.9; From 4.9.0 · fixed in 4.9.14; From 4.8.0 · fixed in 4.8.13; From 4.7.0 · fixed in 4.7.17; From 4.6.0 · fixed in 4.6.18; From 4.5.0 · fixed in 4.5.21; From 4.4.0 · fixed in 4.4.22; From 4.3.0 · fixed in 4.3.23; From 4.2.0 · fixed in 4.2.27; From 4.1.0 · fixed in 4.1.30; From 4.0.0 · fixed in 4.0.30; From 3.9.0 · fixed in 3.9.31; From 3.8.0 · fixed in 3.8.33; From 3.7.0 · fixed in 3.7.33