--- title: "CVE-2026-103065: Themeum Kirki - Broken Access Control" description: "Themeum Kirki <= 6.3.1 contains an access control vulnerability caused by improper validation of specified quantity in input, letting attackers access functionality not properly constrained by ACLs, exploit requires no special privileges." url: https://panop.io/threat-heartbeat/CVE-2026-103065/ --- # CVE-2026-103065 Themeum Kirki - Broken Access Control Themeum Kirki <= 6.3.1 contains an access control vulnerability caused by improper validation of specified quantity in input, letting attackers access functionality not properly constrained by ACLs, exploit requires no special privileges. CVSS base score 8.2 /10 High CISA KEV Not listed Public exploit None known Authentication Not required EPSS 0.21% chance of exploitation in 30 days [View the NVD record ↗](https://nvd.nist.gov/vuln/detail/CVE-2026-103065) ## Details Type Broken Access Control Impact Broken Access Control CVSS vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N Published 3 October 2026 Updated 15 October 2026 Weakness [CWE-1284](https://cwe.mitre.org/data/definitions/1284.html) ## Vendor fix Update to the latest version beyond 6.3.1. Patching closes this CVE. It does not tell you which of your systems run the affected version, or what else is exposed alongside them. ## References - [https://nvd.nist.gov/vuln/detail/CVE-2026-103065](https://nvd.nist.gov/vuln/detail/CVE-2026-103065) - [https://patchstack.com/database/wordpress/plugin/kirki/vulnerability/wordpress-kirki-plugin-6-3-1-arbitrary-code-execution-vulnerability?\_s\_id=cve](https://patchstack.com/database/wordpress/plugin/kirki/vulnerability/wordpress-kirki-plugin-6-3-1-arbitrary-code-execution-vulnerability?_s_id=cve) [← All CVEs](https://panop.io/threat-heartbeat/) ## What this record can't tell you - Whether you run the affected software, and where - Whether an attacker can actually reach and exploit it - The misconfigurations that never get a CVE number - What it would cost the business, ranked into what to fix first Panop answers these inside your environment, for this CVE and every other finding. [Book a demo](https://panop.io/demo)