Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain access to a Kirki field input
-
DeliveryStore crafted XSS payload in option
-
ExploitVictim loads rendered page/admin view
-
ExecutionScript executes in victim session
-
ImpactHijack session or act as victim
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires the attacker to first store a malicious value into a Kirki-managed field/option and then requires a victim to load the page or admin screen that renders it (UI:R - user interaction is mandatory, which limits opportunistic mass exploitation). The affected surface exists only where the Themeum Kirki framework is installed and active (bundled with the theme or as a standalone plugin) at version 6.0.11 or earlier. The CVSS vector states PR:N, but the description does not identify the injection endpoint; if storing the payload in fact needs an authenticated Customizer/option-write capability, the practical prerequisite is a valid low-privilege account - verify the exact injection path with Patchstack before assuming unauthenticated write is possible. |
| Impact | The Patchstack-assigned CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L, base 7.1) describes network-reachable, low-complexity exploitation requiring victim interaction, with limited confidentiality, integrity, and availability impact and a scope change - consistent with typical stored XSS. No EPSS score, SSVC decision, POC, or KEV signal was provided, so exploitation probability cannot be quantified from the input and should be treated as unknown rather than high. One point of tension: the vector lists PR:N (no privileges), yet stored XSS in a Customizer framework normally requires some authenticated capability to write the option that carries the payload; the source description does not state the injection path, so the true privilege requirement is unconfirmed and PR:N may overstate reachability. Net assessment: a genuine but moderate-severity issue - routine-patch priority for sites running Kirki, not an emergency unless corroborating exploitation data emerges. |
| Exploit ScenarioDerived | An actor with the ability to write a Kirki-backed option (for example a lower-privileged user in a multi-author or agency-managed WordPress site) saves a field value containing a script payload; when an administrator or another user later opens the page or Customizer view that renders the value, the script executes in their authenticated session and can perform actions such as session theft or admin-context requests. Network-reachable and low-complexity per CVSS, but requiring that victim to view the tainted content (UI:R). No public POC is referenced in the available data. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jul 13, 2026
Stored cross-site scripting in the Themeum Kirki WordPress customizer framework (versions through 6.0.11) lets an attacker persist malicious script that executes in the browsers of users who later view the affected page or admin screen. Because the CVSS scope is marked changed (S:C), a successful payload can act beyond the vulnerable component's boundary, affecting whoever renders the stored input. There is no public exploit identified at time of analysis and the issue is not listed in CISA KEV.
RemediationAI
No vendor-released patch version is identified at time of analysis - the input names only the vulnerable ceiling (<= 6.0.11) and no fixed release, so upgrade to the next Kirki release above 6.0.11 once the maintainer publishes it and confirm the fix against the Patchstack advisory at https://patchstack.com/database/Wordpress/Plugin/kirki/vulnerability/wordpress-kirki-plugin-6-0-11-cross-site-scripting-xss-vulnerability. Until a fixed version is confirmed, restrict who can edit Customizer/theme options carrying Kirki fields to trusted administrators only, review existing stored option values for injected markup, and consider a WAF or virtual-patching rule (Patchstack offers this) to filter script payloads in the affected fields; the trade-off is that tightening editor capabilities may block legitimate low-privilege customization workflows. If Kirki is only a bundled dependency and unused, removing it eliminates the exposure at the cost of theme features that rely on it.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Kirki (cpe:2.3:a:themeum:kirki) is a widely used toolkit/framework that extends the WordPress Customizer with additional control types, fields, and styling options, and is bundled or depended upon by many commercial and free themes. The flaw is CWE-79 (Improper Neutralization of Input During Web Page Generation), meaning user-supplied input is written into generated HTML without adequate output encoding or sanitization. In a stored variant, the tainted value is saved server-side (e.g. a customizer/theme option or field value) and later reflected into a page or admin view, so the browser interprets attacker markup as executable script rather than data.
Know when Kirki gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
Stored XSS in a Customizer framework realistically needs a low-privilege account to write the option (PR:L), still needs a victim to view it (UI:R), and crosses component scope (S:C).
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
DescriptionCVE.org
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Themeum Kirki kirki allows Stored XSS.This issue affects Kirki: from n/a through <= 6.0.11.
Executive ViewAI
Themeum Kirki, a critical WordPress customizer plugin affecting thousands of organizations, contains a stored cross-site scripting flaw allowing attackers to inject persistent malicious code that executes when administrators and site visitors access affected pages or customization panels. Organizations using vulnerable versions (6.0.11 and earlier) face elevated risk of administrator account compromise, malware injection, and unauthorized data theft impacting both internal staff and external users.
No vendor-released patch identified at time of analysis. Interim mitigations include: restrict customizer access to trusted administrators, implement network-level Content Security Policy and X-Frame-Options headers, deploy Web Application Firewall rules targeting script injection patterns, use WordPress security plugins with active XSS detection and sanitization, and conduct regular manual audits of all customization settings for injected code.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
Server-Side Request Forgery in the Kirki WordPress plugin before 6.0.12 allows unauthenticated attackers to coerce the s
SQL injection in the Kirki WordPress plugin before version 6.0.13 enables unauthenticated remote attackers to read arbit
Broken access control in the Themeum Kirki WordPress customizer framework (versions up to and including 6.0.13) allows r
PHP Object Injection in the Kirki WordPress plugin before 6.0.13 enables a two-stage attack where unauthenticated users
Stored cross-site scripting in the Kirki WordPress plugin before 6.3.0 allows unauthenticated remote attackers to persis
Arbitrary file upload via malformed archive in the Kirki WordPress customizer plugin (all versions before 6.2.3) allows
Stored cross-site scripting in the Kirki WordPress plugin affects versions 6.0.0 through 6.3.0, which allow SVG files to
SQL injection in the Kirki WordPress plugin (versions 6.0.0 through <6.3.0) enables authenticated users with editor-leve
Unauthenticated shortcode injection in Kirki WordPress plugin (all versions before 6.2.1) allows any remote attacker to
Object injection in the Themeum Kirki WordPress customizer framework (all versions through 6.0.12) allows attackers to a
Blind SQL injection in the Themeum Kirki WordPress customizer framework (all versions up to and including 6.0.12) lets r
Kirki WordPress Customizer Framework plugin before 6.0.14 exposes registered user email addresses, comment author emails
EUVD-2026-43376
NVD
CVE.org
EPSS
Vulnrichment
VulDB
GitHub PoC
Exploit-DB