CVE-2026-97640 json
WPConsent <= 1.1.9 - Unauthenticated Stored Cross-Site Scripting via Comment Content via Simple HTML DOM Parser Noise-Key Restoration (mXSS)
published 2026-10-16 24 d ago modified 2026-10-16 23 d ago also EUVD-2026-102799
- cvss
- 7.2
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 15%
- public exploits
- 0
- none known
Summary
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.
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 23 d ago
Exploit prediction
0.24% chance of exploitation in the next 30 days, higher than 15% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.2 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N |
Affected products
- smub WPConsent – Cookie Banner & Cookie Consent for Privacy Compliance (GDPR / CCPA / EU Compliance Cookie Notice)
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/e92b4189-bd07-4d29-8fe1-e9de60107e70?source=cve
- plugins.trac.wordpress.org /browser/wpconsent-cookies-banner-privacy-suite/tags/1.1.9/lib/simplehtmldom/class-wpconsent-simple-html-dom.p
- plugins.trac.wordpress.org /browser/wpconsent-cookies-banner-privacy-suite/tags/1.1.9/lib/simplehtmldom/class-wpconsent-simple-html-dom.p
- plugins.trac.wordpress.org /browser/wpconsent-cookies-banner-privacy-suite/tags/1.1.9/lib/simplehtmldom/class-wpconsent-simple-html-dom.p
- plugins.trac.wordpress.org /browser/wpconsent-cookies-banner-privacy-suite/tags/1.1.9/includes/class-wpconsent-cookie-blocking.php#L107
- plugins.trac.wordpress.org /browser/wpconsent-cookies-banner-privacy-suite/tags/1.1.9/includes/class-wpconsent-cookie-blocking.php#L222
- plugins.trac.wordpress.org /changeset?reponame=&new=3734409%40wpconsent-cookies-banner-privacy-suite&old=3676065%40wpconsent-cookies-bann
- plugins.trac.wordpress.org /changeset/3734401/wpconsent-cookies-banner-privacy-suite/trunk/lib/simplehtmldom/class-wpconsent-simple-html-
Sources
- CVE List CVE-2026-97640
- NVD CVE-2026-97640
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.