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.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Fix
- Fixed in 6.4.1
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
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.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original 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.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Themeum Kirki
fixed in 6.4.1
References 2
Questions about CVE-2026-112347
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: vulncheck.com
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: vulncheck.com
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: vulncheck.com
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: cve.now feed data