# CVE-2026-12720: Kirki < 6.0.13 - Unauthenticated PHP Object Injection

> Unauthenticated attackers can inject PHP objects via stored data, potentially leading to remote code execution when an administrator reviews the data.

- **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:** 31 Jul 2026
- **Updated:** 31 Jul 2026
- **Also known as:** GHSA-rpvq-6gf9-58vg

## What is CVE-2026-12720?

CVE-2026-12720 is a high-severity unsafe deserialization vulnerability in Unknown Kirki, published on 31 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.13 does not restrict which classes may be instantiated when it deserialises data that unauthenticated users can store, leading to PHP Object Injection that is triggered when an administrator later reviews the stored data. With a suitable gadget chain present on the site (via another installed Kirki  WordPress plugin before 6.0.13, , or an outdated WordPress version), this could be leveraged to perform a variety of attacks, such as remote code execution.

Weakness: CWE-502 (Deserialization of Untrusted Data)

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


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

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

## Is CVE-2026-12720 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-12720 is a high-severity unsafe deserialization vulnerability in Unknown Kirki, published on 31 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: There is no known exploitation of CVE-2026-12720 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-12720/ (Markdown: https://insights.sbomify.com/CVE-2026-12720/index.md)
```

## Sources

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

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