Unauthenticated post disclosure via unchecked context key
Published Jul 24, 2026 · Updated Jul 24, 2026
Authorization bypass in Themeum Kirki 6.0.14 and earlier allows remote attackers to read nonpublic WordPress post content. The frontend collection REST path accepts an arbitrary post ID through the context key and processes an attacker-controlled block template without checking access to the referenced post. Unauthenticated network access is sufficient, and disclosure includes titles, excerpts, and full content from draft, pending, private, password-protected, or trashed posts.
Summary
What happened
Authorization bypass in Themeum Kirki 6.0.14 and earlier allows remote attackers to read nonpublic WordPress post content. The frontend collection REST path accepts an arbitrary post ID through the context key and processes an attacker-controlled block template without checking access to the referenced post. Unauthenticated network access is sufficient, and disclosure includes titles, excerpts, and full content from draft, pending, private, password-protected, or trashed posts.
The record
- CVE
- CVE-2026-13464
- Published
- Jul 24, 2026
- Updated
- Jul 24, 2026
- Vendor
- Themeum
- Product
- Kirki
- Classifications
- CWE-639, T1213
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 24, 2026CVE publishedPublication date reported by the CVE source.
- Jul 24, 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=0 <=6.0.14
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