CVE-2026-14572 themeum CVE debrief

Who should care

WordPress administrators, security teams, and users with the kirki_content_access capability should assess exposure and prioritize remediation. This vulnerability affects operators managing WordPress deployments with the Kirki plugin, particularly those with untrusted users or where administrators have granted the kirki_content_access capability. Security teams should review compensating controls and monitor for suspicious activity.

Why it matters

The Kirki plugin vulnerability allows authenticated attackers to inject malicious scripts, potentially leading to security breaches and data exposure. WordPress administrators and security teams should assess exposure and prioritize remediation.

• Authenticated attackers can inject arbitrary web scripts in pages
• Injected scripts execute when a user accesses an injected page
• Requires verification of administrator accounts and capabilities
• Remediation priority for WordPress installations using affected plugin versions

Technical summary

The Kirki – Freeform Page Builder, Website Builder & Customizer plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Page Builder Text Content in all versions up to, and including, 6.2.0. This is due to insufficient input sanitization and output escaping, allowing authenticated attackers with the kirki_content_access capability to inject arbitrary web scripts. The vulnerability requires verification of administrator accounts and capabilities to prevent unauthorized access. Affected WordPress installations should be assessed for exposure, and remediation should be prioritized.

Defensive priority

Assess exposure and prioritize remediation for WordPress installations using the Kirki plugin, especially those with untrusted users or where administrators have granted the kirki_content_access capability.

Recommended defensive actions

• Assess exposure by checking if the Kirki plugin version is 6.2.0 or earlier
• Prioritize remediation or apply compensating controls for WordPress installations using the affected plugin versions
• Monitor for suspicious activity or injected scripts on affected pages
• Verify administrator accounts and capabilities to prevent unauthorized access
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.

Evidence notes

The CVE record and source item provide details on the vulnerability, affected versions, and references to vendor information. Evidence is limited to public sources and may not reflect the full scope or impact. Defenders should verify affected deployments, assess exposure, and review vendor guidance for remediation steps. Limited additional information is available from public sources.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.