Authenticated private-content access via block-editor authorization bypass
Published Sep 9, 2021 · Updated Aug 4, 2024
Authorization bypass in WordPress 5.8 beta 1 allows remote authenticated users to view private post types and data through the block editor. The published advisory does not identify the affected function or explain how the block editor fails to enforce the underlying content permissions. An account lacking permission to view the targeted private content is required; the disclosed impact is unauthorized reading or privilege expansion within the editor.
Summary
What happened
Authorization bypass in WordPress 5.8 beta 1 allows remote authenticated users to view private post types and data through the block editor. The published advisory does not identify the affected function or explain how the block editor fails to enforce the underlying content permissions. An account lacking permission to view the targeted private content is required; the disclosed impact is unauthorized reading or privilege expansion within the editor.
The record
- CVE
- CVE-2021-39203
- Published
- Sep 9, 2021
- Updated
- Aug 4, 2024
- Vendor
- WordPress.org
- Product
- WordPress
- Classifications
- CWE-200, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 9, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.8 beta 1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo