CVE-2026-115814: Kirki <= 6.4.1 - Unauthenticated Stored Cross-Site Scripting via Comment Attribute via Migration Convert Workflow
The Kirki – Freeform Page Builder, Website Builder & Customizer plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'comment (title attribute of <abbr>)' parameter in all versions up to, and including, 6.4.1 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. Successful exploitation requires an administrator to run the Kirki Convert (migration) workflow on a page containing the attacker's approved comment, as the browser-side DOM parser decodes the kses-allowed abbr title attribute value into a raw XSS payload that is then persisted without sanitization and later rendered unescaped. Successful exploitation additionally requires an action by an administrator — the attacker cannot trigger the vulnerability on their own.
Affected Software
Event History
Frequently Asked Questions
Which installations are affected?
Kirki versions up to and including 6.4.1 are affected. The issue applies when the Kirki Convert migration workflow is used on a page containing an attacker’s approved comment.
Can an attacker exploit this without an account or administrator access?
An attacker does not need to be authenticated to supply the malicious content, but cannot complete exploitation alone. An administrator must run the Kirki Convert workflow on the affected page.
What administrator action makes the injected script persist?
Running the Kirki Convert migration workflow causes the browser-side DOM parser to decode the allowed abbr title attribute value. The resulting payload is then persisted without sanitization and later rendered unescaped.
What can be done while patching is unavailable?
Avoid running the Kirki Convert workflow on pages that contain untrusted or attacker-approved comments. Review comments on pages scheduled for conversion before an administrator starts the migration workflow.
How can I assess whether exploitation may have occurred?
Check whether an affected Kirki version was in use and whether administrators ran the Kirki Convert workflow on pages containing approved comments from untrusted sources. Those conditions are required for the payload to be persisted and later execute when users access the page.