sales@hackhalt.com

Home / Threats / CVE-2026-84225

Kirki - Security Vulnerability (CVE-2026-84225)

CVE-2026-84225

Vulnerability CVE-2026-84225 PLUGIN kirki LOW

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.

CVE-2026-84225

LOW CVSS 2.2 Published 2026-09-05 Updated 2026-09-08
AI Risk Low (20/100) Active Exploit: No strong signal Published Exploit: No public exploit references Priority: P5 Monitor
Severity Band LOW
CVSS Vector CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:L/A:N
Affected Components 1
Reference Links 1
AI Risk Engine Low (20/100)
Exploitability Low
Active Exploitation No strong signal
Published Exploit Status No public exploit references

Threat Timeline

  1. 2026-09-05 CVE published and first recorded in the threat feed.
  2. 2026-09-08 Record updated with latest vulnerability metadata.
  3. 2026-09-07 AI technical context refreshed for mitigation and impact guidance.
  4. Now Monitoring for follow-up changes, linked references, and new related CVEs.

AI Context

Machine-generated threat intelligence

AI Updated 30 days ago

AI enriched 30 days ago (2026-09-07 07:05 UTC)

Technical Summary

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.

Potential Impact

Severity is LOW (CVSS 2.2). Depending on deployment context, affected components may be exposed to unauthorized actions or data integrity risk.

Exploitability Assessment

Exploitability is assessed as Low based on severity and technical exposure profile.

Primary risk drivers: severity and technical exposure profile

Mitigation Recommendations

Validate affected product versions, prioritize patching, and monitor references for vendor remediation guidance. If immediate patching is not possible, apply compensating controls and limit exposure of vulnerable surfaces.

Detection & Monitoring

Track authentication anomalies, unexpected file writes, and suspicious plugin API activity around affected components.

Business Impact Lens

AI risk score 20/100 (Low, Low) with priority P5 Monitor. Prioritize remediation where affected components process customer data, admin sessions, or Internet-exposed workflows.

Affected Products

Kirki PLUGIN · kirki Affected: < 6.3.0 Fixed in: 6.3.0

References

What to do about this

Low priority Contained impact, or it needs privileges an attacker would rarely already hold.

Fix it

Update Kirki to 6.3.0 or later.

That is the complete fix. Everything below is what protects you in the meantime.

No Hack Halt control meaningfully contains this one — updating is the remedy. We would rather say so than sell you something that will not help.

Start free

Not sure if you are affected?

Scan your site to see whether it runs Kirki, and at which version.

Free, no installation, no account. It reads what your site already publishes, then tells you which plugins carry known vulnerabilities and what to do about each one.

Scan my site free See what Hack Halt does

Am I affected by this vulnerability?

You are affected if your site runs Kirki. Versions below 6.3.0 are vulnerable; that release and later are not.

How do I fix it?

Update Kirki to version 6.3.0 or later. That is the complete fix.