Quick answers
- Is CVE-2026-84225 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-84225 being exploited in the wild.
- How severe is CVE-2026-84225?
- Low severity, with a CVSS score of 2.2, published 5 September 2026.
- Which products and versions are affected?
- Kirki Kirki 6.0.0 to 6.2.5.
- Is there a fix for CVE-2026-84225?
- A patch was published on 2026-09-05: Fixed in version 6.3.0 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-84225 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-84225?
- Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The Kirki plugin versions 6.0.0 through 6.2.5 fail to validate user permissions before processing REST API requests to modify collaboration comment status. Specifically, the /kirki/v1/collaboration-comments/resolve, /read, /unread, /read-all, and /resolve-all endpoints do not check whether the authenticated user owns the comment or has access to the associated page. An authenticated user with content-level page builder access can craft PUT requests to change comment state on any post, bypassing ownership and access control checks that are correctly enforced on the delete endpoint. The vulnerability is an Insecure Direct Object Reference (IDOR) requiring authentication and administrative role configuration, but allowing lateral privilege escalation within the plugin's permission model. Version 6.3.0 and later include the necessary authorization and ownership validation.
Affected products
- Kirki Kirki 6.0.0 to 6.2.5
Timeline
- 2026-09-03: disclosed
- 2026-09-05: patched: Fixed in version 6.3.0