Authenticated comment status changes via missing object authorization
Published Sep 5, 2026 · Updated Sep 6, 2026
Authorization bypass in Themeum Kirki 6.0.0 through 6.2.5 allows remote authenticated users to change collaboration comment states. The collaboration comment state-change path accepts a selected comment without checking that the caller may act on that comment or access its page. An administrator must first grant the account content-level page-builder access; the account can then alter other users’ comment workflow state, not page content.
Summary
What happened
Authorization bypass in Themeum Kirki 6.0.0 through 6.2.5 allows remote authenticated users to change collaboration comment states. The collaboration comment state-change path accepts a selected comment without checking that the caller may act on that comment or access its page. An administrator must first grant the account content-level page-builder access; the account can then alter other users’ comment workflow state, not page content.
The record
- CVE
- CVE-2026-84225
- Published
- Sep 5, 2026
- Updated
- Sep 6, 2026
- Vendor
- Themeum
- Product
- Kirki
- Classifications
- CWE-639, T1565.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 5, 2026CVE publishedPublication date reported by the CVE source.
- Sep 6, 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=6.0.0 <6.3.0
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