# CVE-2026-84224: Kirki < 6.3.2 - Editor+ Blind SSRF via Remote Template URL

> Editors can exploit unvalidated remote template URLs to perform Server-Side Request Forgery, accessing internal services and probing network availability.

- **Severity:** Medium 4.1 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/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:** 9 Oct 2026
- **Updated:** 9 Oct 2026
- **Also known as:** GHSA-w2rx-5q64-f3mg

## What is CVE-2026-84224?

CVE-2026-84224 is a medium-severity server-side request forgery vulnerability in Unknown Kirki, published on 9 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The Kirki WordPress plugin before 6.3.2 does not validate the host of a URL it is given before fetching it, allowing users with editor-level access and above to make the site issue requests to internal services that are not otherwise reachable, and to tell which of those are live from the response.

Weakness: CWE-918 (Server-Side Request Forgery)

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


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

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

## Is CVE-2026-84224 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-84224 is a medium-severity server-side request forgery vulnerability in Unknown Kirki, published on 9 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-84224 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-84224/ (Markdown: https://insights.sbomify.com/CVE-2026-84224/index.md)
```

## Sources

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

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