# CVE-2026-84225: Kirki 6.0.0 - 6.2.5 - Authenticated Collaboration Comment Status Modification via IDOR

> Authenticated users with page builder access can modify other users' collaboration comments due to missing authorization checks.

- **Severity:** Low 2.2 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Sep 2026
- **Updated:** 6 Sep 2026
- **Also known as:** GHSA-gf6x-qf8h-8g89

## What is CVE-2026-84225?

CVE-2026-84225 is a low-severity missing authorization vulnerability in Unknown Kirki, published on 5 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The Kirki  WordPress plugin before 6.3.0 does not check that a user is allowed to act on a collaboration comment before changing its state, allowing users whom an administrator has granted content-level access to the page builder to modify comments left by other users, including on pages they cannot themselves open.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-84225?


## How do I fix CVE-2026-84225?

No fix has been published for CVE-2026-84225 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-84225 being exploited?

There is no known exploitation of CVE-2026-84225 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-84225 and fix it if it is affected.

What it is: CVE-2026-84225 is a low-severity missing authorization vulnerability in Unknown Kirki, published on 5 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-84225 in the wild and no public exploit code.

Affected product: Unknown Kirki. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-84225/ (Markdown: https://insights.sbomify.com/CVE-2026-84225/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-84225
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-84225
- OSV: https://osv.dev/vulnerability/CVE-2026-84225

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-84225/
Summaries are generated and may contain mistakes; the official description above is the record.