Live › vulnerability › CVE-2026-97640
Go to dashboardThe WPConsent cookie consent plugin for WordPress, up to and including 1.1.9, fails to sanitize comment content, so an unauthenticated visitor can plant a stored mXSS payload that runs JavaScript in the browser of anyone who loads the affected page. The attack needs two coordinated comments and the Script Blocking feature turned on.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
WordPress sites running WPConsent 1.1.9 or earlier with the Script Blocking feature enabled and public comments accepted are exposed, because the injected script is stored and runs for later visitors. Sites without the plugin, with an older or newer version, or with Script Blocking off are not affected by this chain.
No product ranges from the sources yet.
wp plugin get wpconsent --field=version1.1.9 once a patched release is available; the sources do not name a fixed versionEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
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 wpconsent_debug=1 request.
This page as .md · .json · in your agent: get_signal("CVE-2026-97640")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.