Description
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.
Published: 2026-10-16
Score: 7.2 High
EPSS: < 1% Very Low
KEV: No
Impact: Unauthenticated Stored Cross‑Site Scripting
Action: Immediate Patch
AI Analysis

Impact

WPConsent’s Simple HTML DOM Parser fails to properly sanitize comment content. An unauthenticated user can submit two coordinated comments—one embedding an event‑handler inside an allowed <code> element and another placing a deterministic noise‑restoration key inside an <abbr title=> attribute—while the Script Blocking feature is enabled. This allows the attacker to inject arbitrary JavaScript that is stored and served to every visitor. The resulting stored cross‑site scripting can compromise user sessions, steal credentials, or modify the site’s content, representing a serious integrity threat.

Affected Systems

All installations of the WPConsent – Cookie Banner & Cookie Consent for Privacy Compliance plugin for WordPress, including every version from its inception through 1.1.9, are affected. WordPress sites that use this plugin and have the Script Blocking option turned on are vulnerable.

Risk and Exploitability

The CVSS base score of 7.2 denotes a high impact vulnerability. The EPSS score of < 1% indicates a very low probability of exploitation, and the issue is not listed in CISA’s KEV catalog; the attack can be performed without authentication by submitting the crafted comments. The requirement for the Script Blocking feature does limit the attack surface, but many sites enable it to meet EU/US compliance, making exploitation plausible for motivated attackers who can target vulnerable comment forms.

Generated by OpenCVE AI on October 16, 2026 at 15:54 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade WPConsent to the latest released version, which removes the insecure HTML parsing logic and implements proper input validation and output escaping.
  • If an immediate upgrade is not feasible, disable the plugin’s Script Blocking feature or block unauthenticated comment posting to break the two‑step injection chain.
  • Apply a web application firewall rule that filters out event‑handler payloads in <code> tags and sanitizes <abbr title=> attributes, or configure the site to accept only approved comment content.

Generated by OpenCVE AI on October 16, 2026 at 15:54 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Fri, 16 Oct 2026 15:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Fri, 16 Oct 2026 07:00:00 +0000

Type Values Removed Values Added
Description 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 &lt;code&gt; element and one placing the deterministic ___noise___ restoration key inside an allowed &lt;abbr title=""&gt; attribute — with the key offset confirmable via an unauthenticated wpconsent_debug=1 request.
Title WPConsent <= 1.1.9 - Unauthenticated Stored Cross-Site Scripting via Comment Content via Simple HTML DOM Parser Noise-Key Restoration (mXSS)
Weaknesses CWE-79
References
Metrics cvssV3_1

{'score': 7.2, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N'}


Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: Wordfence

Published:

Updated: 2026-10-16T14:39:02.103Z

Reserved: 2026-09-24T17:36:10.171Z

Link: CVE-2026-97640

cve-icon Vulnrichment

Updated: 2026-10-16T14:33:51.464Z

cve-icon NVD

Status : Deferred

Published: 2026-10-16T07:17:14.823

Modified: 2026-10-16T15:17:38.253

Link: CVE-2026-97640

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-10-16T16:00:12Z

Weaknesses
  • CWE-79

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