Broken object-level access control exists in the page REST API. The endpoint "/wp-json/kirki/v1/pages/{page id}" and the handlers `save page data()`, `duplicate()`, and `delete()` in PageController.php use a coarse role-to-access middleware check but fail to perform a per-object WordPress capability check. An authenticated user with Kirki edit access, which is granted to the Editor role by default, can 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. This can be achieved by manipulating the unrestricted `post status` field, potentially exposing private or draft content or removing published content.