# CVE-2026-112347: Kirki page builder broken object-level access control in REST API

Source: https://junglewise.ai/threats/cve-2026-112347-kirki-plugin-for-wordpress-before-6-4-1-contains-a-broken-object  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-30. Updated: 2026-10-30  
License: CC BY 4.0 with a link back

CVE-2026-112347 · Severity: high · CVSS 7.6 · Published 2026-10-30

Kirki is a visual page builder plugin for WordPress that allows designers to create websites without coding. The vulnerability allows authenticated editors to modify, delete, or change the publication status of any WordPress post or product they don't own, potentially exposing private content or taking down published material. An attacker with basic editor privileges granted by default can exploit this flaw to compromise the integrity of website content across multiple post types.

Technologies: [Themeum Kirki](https://junglewise.ai/threats/technologies/kirki). Vendors: [Themeum](https://junglewise.ai/threats/vendors/themeum).

## Quick answers

**Is CVE-2026-112347 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-112347 being exploited in the wild.

**How severe is CVE-2026-112347?** High severity, with a CVSS score of 7.6, published 30 October 2026.

**Which products and versions are affected?** Themeum Kirki before 6.4.1.

**Is there a fix for CVE-2026-112347?** Yes: fixed in 6.4.1. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-112347 attacked?** It is attacked over the network, in a web application.

**Am I affected by CVE-2026-112347?** Check whether you run Themeum Kirki at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- Fixed in 6.4.1

## Technical details

The REST API endpoint PUT /wp-json/kirki/v1/pages/{page_id} and its handlers in PageController.php perform only a coarse role-based access check instead of per-object WordPress capability verification. An authenticated Editor (default Kirki edit access) can craft requests to modify the title, slug, and post_status fields of any non-trashed post across all post types including custom types and WooCommerce products. The vulnerability requires network access and valid authentication but no user interaction from the target.

## Affected products

- Themeum Kirki before 6.4.1

## Timeline

- 2026-10-30: disclosed

## References

- [https://wordpress.org/plugins/kirki/](https://wordpress.org/plugins/kirki/)
- [https://www.vulncheck.com/advisories/kirki-wordpress-plugin-broken-object-level-access-control-via-page-api](https://www.vulncheck.com/advisories/kirki-wordpress-plugin-broken-object-level-access-control-via-page-api)

## Related threats

- [Kirki reCAPTCHA bypass in form submission](https://junglewise.ai/threats/cve-2026-112348-kirki-plugin-for-wordpress-before-6-2-5-contains-a-recaptcha)
- [Themeum Kirki cross-site scripting vulnerability in HTML tag handling](https://junglewise.ai/threats/cve-2026-42694-improper-neutralization-of-script-related-html-tags-in-a-web-page)
- [Themeum Kirki arbitrary code execution in input validation](https://junglewise.ai/threats/cve-2026-103065-improper-validation-of-specified-quantity-in-input-vulnerability)
- [Themeum Kirki arbitrary file deletion in Editor component](https://junglewise.ai/threats/cve-2026-65436-themeum-kirki-arbitrary-file-deletion-in-editor-component)
- [Themeum Kirki missing authorization in access control](https://junglewise.ai/threats/cve-2026-57727-themeum-kirki-missing-authorization-in-access-control)