# CVE-2026-84219: Kirki 6.2.1 - 6.2.5 - Unauthenticated Stored XSS via HTML Entity Decoding

> Unauthenticated attackers can inject JavaScript via comments that executes in admin sessions, potentially leading to site takeover.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 6 Sep 2026
- **Updated:** 6 Sep 2026
- **Also known as:** GHSA-5jh7-hrj4-qc2f

## What is CVE-2026-84219?

CVE-2026-84219 is a high-severity cross-site scripting vulnerability in Unknown Kirki, published on 6 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The Kirki  WordPress plugin before 6.3.0 does not hold back every spelling of the HTML entities it decodes when rendering, allowing unauthenticated users to store JavaScript in a comment which then runs in the session of anyone viewing a page that displays it, including an administrator, and on every page of the site when its header or footer is built to show comments.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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


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

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

## Is CVE-2026-84219 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-84219 is a high-severity cross-site scripting vulnerability in Unknown Kirki, published on 6 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-84219 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-84219/ (Markdown: https://insights.sbomify.com/CVE-2026-84219/index.md)
```

## Sources

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

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