Kirki permits unauthenticated stored XSS through comments
Kirki through 6.2.0 does not sufficiently sanitize and escape the comment parameter before stored output. An unauthenticated attacker can inject script into a page, and the code executes whenever a user accesses the affected page. The authoritative export identifies the parameter but does not disclose the submission endpoint, storage function, or output context.
- Component
- Kirki – Freeform Page Builder, Website Builder & Customizer
- Affected
- <= 6.2.0
- Safe version
- See mitigation notes
- Published
- Sep 11, 2026
This CVE was published Sep 11, 2026 and is one of 1 known issue for this plugin.
Update, patch or deactivate.
The authoritative export does not identify the first fixed release. Update to a vendor-confirmed release after 6.2.0, moderate untrusted comments until remediated, and ensure comment input is sanitized and escaped for its exact output context.
No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.
Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.
Technical description
The Kirki – Freeform Page Builder, Website Builder & Customizer plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘comment’ parameter in all versions up to, and including, 6.2.0 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N