CVE-2026-97640: WPConsent <= 1.1.9 - Unauthenticated Stored Cross-Site Scripting via Comment Content via Simple HTML DOM Parser Noise-Key Restoration (mXSS)
The WPConsent – Cookie Banner & Cookie Consent for Privacy Compliance (GDPR / CCPA / EU Compliance Cookie Notice) plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Comment Content via Simple HTML DOM Parser Noise-Key Restoration (mXSS) in all versions up to, and including, 1.1.9 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. This requires the Script Blocking feature to be enabled, and the exploit chain depends on an attacker submitting two coordinated comments — one embedding event-handler syntax inside an allowed <code> element and one placing the deterministic noise restoration key inside an allowed <abbr title=""> attribute — with the key offset confirmable via an unauthenticated wpconsentdebug=1 request.
Affected Software
Event History
Frequently Asked Questions
Which deployments are exposed to this issue?
WPConsent versions up to and including 1.1.9 are affected when the Script Blocking feature is enabled. The vulnerable path processes comment content, so sites that accept attacker-controlled comments are the practical exposure point.
Does exploitation require an account or user interaction?
No attacker account or prior authentication is required. An attacker must submit two coordinated comments and can confirm the restoration-key offset through an unauthenticated request using wpconsent_debug=1; the injected script executes when someone visits an affected page.
What conditions must an exploit meet?
The exploit requires one comment containing event-handler syntax within an allowed code element and another containing the deterministic ___noise___ restoration key in an allowed abbr title attribute. Both comments are required for the described exploit chain.