Kirki comment rendering permits unauthenticated stored XSS
Kirki 6.2.1 through 6.2.x does not block every spelling of the HTML entities it decodes during rendering. An unauthenticated commenter can store JavaScript that executes for anyone viewing an affected page, including an Administrator; when comments are incorporated into a Kirki-built header or footer, the payload can execute site-wide.
- Component
- Kirki
- Plugin slug
kirki- Affected
- 6.2.1 to < 6.3.0
- Safe version
6.3.0- Published
- Sep 06, 2026
This CVE was published Sep 06, 2026 and is one of 42 known issues for this plugin.
Update, patch or deactivate.
Update to Kirki 6.3.0 or later, remove malicious comments, and invalidate privileged sessions if administrators viewed affected pages.
A safe version is available, so updating to that version or later is the preferred remediation. If an immediate update is not practical, consider a targeted application patch or temporarily restricting the affected functionality.
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 WordPress plugin before 6.3.0 does not hold back every spelling of the HTML entities it decodes when rendering, allowing unauthenticated users to store JavaScript in a comment which then runs in the session of anyone viewing a page that displays it, including an administrator, and on every page of the site when its header or footer is built to show comments.
CVE / CNA vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H