# CVE-2026-74992: Kirki < 6.2.3 - Editor+ Stored XSS via Font Zip Upload

> Editors can upload malicious archives to trigger Stored XSS and potential remote code execution in the Kirki WordPress plugin.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 20 Aug 2026
- **Updated:** 20 Aug 2026
- **Also known as:** GHSA-7grj-4mf9-j4px

## What is CVE-2026-74992?

CVE-2026-74992 is a medium-severity cross-site scripting vulnerability in Unknown Kirki, published on 20 Aug 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

The Kirki  WordPress plugin before 6.2.3 does not properly validate the files contained in archives uploaded by users with the Editor role, and does not remove all unwanted files after extracting them, allowing such users to upload arbitrary files to a web accessible directory, leading to Stored XSS as well as RCE on some server configurations.

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

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


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

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

## Is CVE-2026-74992 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-74992 is a medium-severity cross-site scripting vulnerability in Unknown Kirki, published on 20 Aug 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-74992 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-74992/ (Markdown: https://insights.sbomify.com/CVE-2026-74992/index.md)
```

## Sources

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

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