# CVE-2026-12724: Kirki < 6.0.12 - Unauthenticated HTML Injection in Password Reset Email via kirki-forgot-password

> Unauthenticated attackers can inject HTML into password reset emails, enabling phishing attacks against registered users.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N`)
- **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:** 20 Jul 2026
- **Updated:** 20 Jul 2026
- **Also known as:** GHSA-xg2c-9mhj-9pvj

## What is CVE-2026-12724?

CVE-2026-12724 is a medium-severity cross-site scripting vulnerability in Unknown Kirki, published on 20 Jul 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.0.12 does not sanitise or escape the email subject and body values supplied in a request before including them in the password-reset email it sends as HTML, allowing unauthenticated users to inject arbitrary HTML into the message delivered to a registered user, which can be used for phishing.

Weakness: CWE-345 (Insufficient Verification of Data Authenticity)

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


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

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

## Is CVE-2026-12724 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-12724 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-12724 is a medium-severity cross-site scripting vulnerability in Unknown Kirki, published on 20 Jul 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-12724 exists.

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-12724/ (Markdown: https://insights.sbomify.com/CVE-2026-12724/index.md)
```

## Sources

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

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