Live › vulnerability › CVE-2026-112347
Kirki for WordPress before 6.4.1 fails to check ownership on its page REST API, so a user with Kirki edit access can modify any non-trashed post or product they do not own. An attacker can expose private or draft content or unpublish live content by changing the post status.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-30 14:30 UTC. All times on this page are UTC.
Sites running Kirki before 6.4.1 that have users with edit access through Kirki, which the Editor role gets by default. Any post type is in scope, including custom post types and WooCommerce products. Sites without Kirki, or running 6.4.1 or later, are not affected.
No product ranges from the sources yet.
wp plugin get kirki --field=version or in the WordPress admin under Plugins./wp-json/kirki/v1/pages/ in the site's REST API index at /wp-json/.6.4.1 or later.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-112347")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.