Kirki: A security weakness
Kirki is affected by a security weakness. The vulnerable path is reachable without authentication. The resulting impact depends on how the affected component exposes the vulnerable operation. The published affected range is < 6.0.12.
- Component
- Kirki
- Plugin slug
kirki- Affected
- < 6.0.12
- Safe version
6.0.12- Published
- Jul 20, 2026
- Weakness
- CWE-862 — Missing Authorization
This CVE was published Jul 20, 2026 and is one of 17 known issues for this plugin.
Update, patch or deactivate.
Update Kirki to 6.0.12 or later, or disable and remove it until a fixed version is available.
A safe version is available, so updating to that version or later is the preferred remediation. If an immediate update is not practical, consider a targeted application patch or temporarily restricting the affected functionality.
Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.
Technical description
The Kirki WordPress plugin before 6.0.12 does not perform any authorisation check on one of its REST routes, allowing unauthenticated users to overwrite the content of arbitrary existing comments and to create pre-approved comments under a spoofed identity, bypassing comment moderation.
CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N