# CVE-2026-84220: Kirki < 6.3.2 - Unauthenticated Arbitrary Shortcode Execution via Comments Collection

> Unauthenticated attackers can execute arbitrary shortcodes and read private custom fields via comments in the Kirki WordPress plugin.

- **Severity:** Medium 4.8 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Oct 2026
- **Updated:** 9 Oct 2026
- **Also known as:** GHSA-wv2j-h628-x2ww

## What is CVE-2026-84220?

CVE-2026-84220 is a medium-severity code injection vulnerability in Unknown Kirki, published on 9 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Kirki WordPress plugin before 6.3.2 does not prevent shortcodes held in comments from being executed when it renders them, and displays comments regardless of their moderation status, allowing unauthenticated visitors to run shortcodes registered on the site and to read private custom fields of the page being viewed.

Weakness: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

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


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

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

## Is CVE-2026-84220 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-84220 is a medium-severity code injection vulnerability in Unknown Kirki, published on 9 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-84220 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-84220/ (Markdown: https://insights.sbomify.com/CVE-2026-84220/index.md)
```

## Sources

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

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