Unauthenticated content disclosure via Authorization header presence
Published Nov 13, 2025 · Updated Nov 13, 2025
Protection mechanism failure in WP Headless CMS Framework 1.15 and earlier allows remote attackers to read restricted content. The request authorization path treats the mere presence of an Authorization header as sufficient to bypass WordPress REST API nonce protection. No credentials or user interaction are required; a crafted network request can expose content otherwise blocked by the nonce check.
Summary
What happened
Protection mechanism failure in WP Headless CMS Framework 1.15 and earlier allows remote attackers to read restricted content. The request authorization path treats the mere presence of an Authorization header as sufficient to bypass WordPress REST API nonce protection. No credentials or user interaction are required; a crafted network request can expose content otherwise blocked by the nonce check.
The record
- CVE
- CVE-2025-11260
- Published
- Nov 13, 2025
- Updated
- Nov 13, 2025
- Vendor
- Ben Moody
- Product
- WP Headless CMS Framework
- Classifications
- CWE-693, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 13, 2025CVE publishedPublication date reported by the CVE source.
- Nov 13, 2025Record 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=* <=1.15
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