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