Restricted-content disclosure via REST collection authorization
Published Sep 23, 2025 · Updated Apr 28, 2026
Authorization failure in WordPress 6.8 through 6.8.2 allows remote authenticated users to read restricted content through the REST API. Collection endpoints using the edit context applied only broad collection-level checks, then serialized posts, terms, and users without per-object edit authorization. Contributor-level access is required; exposure is limited to content and records that the account cannot otherwise edit.
Summary
What happened
Authorization failure in WordPress 6.8 through 6.8.2 allows remote authenticated users to read restricted content through the REST API. Collection endpoints using the edit context applied only broad collection-level checks, then serialized posts, terms, and users without per-object edit authorization. Contributor-level access is required; exposure is limited to content and records that the account cannot otherwise edit.
The record
- CVE
- CVE-2025-58246
- Published
- Sep 23, 2025
- Updated
- Apr 28, 2026
- Vendor
- WordPress.org
- Product
- WordPress
- Classifications
- CWE-201, CAPEC-37, T1213
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 23, 2025CVE publishedPublication date reported by the CVE source.
- Apr 28, 2026Record 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=4.7 <=4.7.30 changes=[{"at":"4.7.31","status":"unaffected"}]
- Affected versionversion=4.8 <=4.8.26 changes=[{"at":"4.8.27","status":"unaffected"}]
- Affected versionversion=4.9 <=4.9.27 changes=[{"at":"4.9.28","status":"unaffected"}]
- Affected versionversion=5.0 <=5.0.23 changes=[{"at":"5.0.24","status":"unaffected"}]
- Affected versionversion=5.1 <=5.1.20 changes=[{"at":"5.1.21","status":"unaffected"}]
- Affected versionversion=5.2 <=5.2.22 changes=[{"at":"5.2.23","status":"unaffected"}]
- Affected versionversion=5.3 <=5.3.19 changes=[{"at":"5.3.20","status":"unaffected"}]
- Affected versionversion=5.4 <=5.4.17 changes=[{"at":"5.4.18","status":"unaffected"}]
- Affected versionversion=5.5 <=5.5.16 changes=[{"at":"5.5.17","status":"unaffected"}]
- Affected versionversion=5.6 <=5.6.15 changes=[{"at":"5.6.16","status":"unaffected"}]
- Affected versionversion=5.7 <=5.7.13 changes=[{"at":"5.7.14","status":"unaffected"}]
- Affected versionversion=5.8 <=5.8.11 changes=[{"at":"5.8.12","status":"unaffected"}]
- Affected versionversion=5.9 <=5.9.11 changes=[{"at":"5.9.12","status":"unaffected"}]
- Affected versionversion=6.0 <=6.0.10 changes=[{"at":"6.0.11","status":"unaffected"}]
- Affected versionversion=6.1 <=6.1.8 changes=[{"at":"6.1.9","status":"unaffected"}]
- Affected versionversion=6.2 <=6.2.7 changes=[{"at":"6.2.8","status":"unaffected"}]
- Affected versionversion=6.3 <=6.3.6 changes=[{"at":"6.3.7","status":"unaffected"}]
- Affected versionversion=6.4 <=6.4.6 changes=[{"at":"6.4.7","status":"unaffected"}]
- Affected versionversion=6.5 <=6.5.6 changes=[{"at":"6.5.7","status":"unaffected"}]
- Affected versionversion=6.6 <=6.6.3 changes=[{"at":"6.6.4","status":"unaffected"}]
- Affected versionversion=6.7 <=6.7.3 changes=[{"at":"6.7.4","status":"unaffected"}]
- Affected versionversion=6.8 <=6.8.2 changes=[{"at":"6.8.3","status":"unaffected"}]
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