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.
Published: 2026-09-06
Score: n/a
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

This flaw allows an unauthenticated user to insert JavaScript code into comments because the plugin fails to neutralize decoded HTML entities. When a page that displays that comment, such as a stored header or footer, is loaded by any visitor—including administrators—the malicious script runs in the context of the user's browser. The vulnerability enables the attacker to steal authentication cookies, deface the site, or redirect users to malicious destinations, thereby compromising confidentiality, integrity, and availability of the site’s front‑end.

Affected Systems

The issue affects the Kirki WordPress plugin versions 6.2.1 through 6.2.5. Any WordPress site using these plugin versions and rendering comments within page headers or footers is susceptible. No other vendors or product families are directly impacted.

Risk and Exploitability

The vulnerability is a stored, unauthenticated XSS that can affect all users who view a page containing the vulnerable comment. While a CVSS score is not published, the nature of XSS typically warrants a high severity assessment. The EPSS score is not available, and the issue is not listed in the CISA KEV catalog. Attackers can exploit this flaw by submitting a malicious comment from any IP address, making it highly accessible. Once the comment is stored, the script propagates to all visitors, including privileged accounts, and continues to affect every subsequent page rendering that comment.

Generated by OpenCVE AI on September 6, 2026 at 07:22 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade the Kirki plugin to version 6.3.0 or newer.
  • Disable comment rendering in headers and footers or use a sanitization routine that removes JavaScript.
  • Deploy a Content Security Policy that blocks inline script execution and disallows unsafe‑eval.

Generated by OpenCVE AI on September 6, 2026 at 07:22 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Sun, 06 Sep 2026 07:45:00 +0000

Type Values Removed Values Added
Weaknesses CWE-79

Sun, 06 Sep 2026 06:30:00 +0000

Type Values Removed Values Added
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.
Title Kirki 6.2.1 - 6.2.5 - Unauthenticated Stored XSS via HTML Entity Decoding
References

Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: WPScan

Published:

Updated: 2026-09-06T06:00:04.619Z

Reserved: 2026-09-01T11:50:19.947Z

Link: CVE-2026-84219

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-09-06T07:16:43.427

Modified: 2026-09-06T07:16:43.427

Link: CVE-2026-84219

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-09-06T07:30:03Z

Weaknesses
  • CWE-79

    Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')