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

> Editors can inject SQL via field IDs to read database contents, including credentials, in the Kirki WordPress plugin.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/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-78r9-6m52-hhpv

## What is CVE-2026-84221?

CVE-2026-84221 is a medium-severity SQL injection 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 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.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

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


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

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

## Is CVE-2026-84221 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-84221 is a medium-severity SQL injection 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-84221 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-84221/ (Markdown: https://insights.sbomify.com/CVE-2026-84221/index.md)
```

## Sources

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

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