Skip to main content

Real Cookie Banner CVE-2026-92977

| EUVDEUVD-2026-91892 HIGH
Cross-site Scripting (XSS) (CWE-79)
2026-10-03 Wordfence GHSA-x9w3-97r6-g49g
7.2
CVSS 3.1 · Vendor: Wordfence
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Submit crafted comment with anchor title payload
  2. Delivery
    Payload survives kses save filter
  3. Exploit
    Comment approved via moderation
  4. Execution
    Plugin regex strips quote at render
  5. Impact
    Script executes in visitor browsers

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK

2 techniques across 2 tactics: Initial Access, Execution

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires (1) the target site to allow comment submission, (2) the crafted anchor-tag/title-attribute payload to pass WordPress's comment kses sanitization at save time, (3) the comment to be approved through the standard comment moderation workflow before public display, and (4) the Real Cookie Banner plugin (≤5.3.5) to render the page so its page-wide regex strips the closing quote delimiter and promotes the payload to an executable attribute. Limiting factors: manual comment moderation is the primary gate - sites requiring human approval of first-time commenters significantly blunt this; sites that auto-approve comments remove that barrier. The attacker needs no authentication (PR:N), but the attack is passive until a victim loads the injected page.

Impact

Signals here conflict in an instructive way. The supplied CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N, base 7.2 HIGH) paints this as a trivially exploitable remote unauthenticated stored XSS, but the description materially undercuts that: the payload only becomes executable through a specific plugin-side regex that strips the closing quote delimiter at render time, AND the malicious comment must first pass WordPress's standard comment moderation workflow before it is publicly displayed. Both of those are real barriers that the AC:L/UI:N rating does not capture - exploitation is not a straightforward one-shot injection against a default install. No EPSS score, KEV listing, or POC availability was provided in the input, so there is no evidence of active exploitation or public exploit code; exploitation status is therefore 'no public exploit identified at time of analysis.' Net assessment: this is a legitimate stored XSS worth patching, but it is a moderate real-world priority rather than an emergency - the moderation gate and the dependency on a specific rendering quirk make opportunistic mass exploitation unlikely. It ranks below an unconditioned PR:N/UI:N stored XSS despite the identical headline score. Verify the moderation assumption against your own site configuration, since sites that auto-approve comments (or auto-approve for previously-approved commenters) remove the primary limiting factor.

Exploit ScenarioDerived

An unauthenticated attacker submits a blog comment containing an anchor tag whose title attribute carries a script payload crafted to survive WordPress's comment kses filter at save time. After the comment is approved through normal moderation, the Real Cookie Banner plugin's page-wide regex strips the closing quote delimiter during rendering, promoting the payload into an executable HTML attribute so the script runs in the browser of every visitor who loads the affected page. No public exploit code was identified in the provided data.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 03, 2026

Stored cross-site scripting in the WordPress plugin Real Cookie Banner: GDPR & ePrivacy Cookie Consent (all versions up to and including 5.3.5) lets unauthenticated commenters plant markup that the plugin's own render-time HTML rewriting later promotes into an executable attribute, running script in the browser of any visitor who loads the injected page. Exploitability is gated by WordPress's standard comment moderation workflow, which is why our assessment conflicts with the vendor-supplied vector: the published CVSS uses AC:L while we assess AC:H (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N) because the payload must survive the comment kses filter at save time and be approved for display before the plugin's page-wide regex strips the closing quote delimiter and activates it. No public exploit code has been identified at time of analysis, and the issue is not confirmed actively exploited (CISA KEV).

RemediationAI

Upstream fix available (changeset/commit); released patched version not independently confirmed - the plugin repository changeset 3710645 (linked via https://plugins.trac.wordpress.org/changeset?reponame=&old=3710645%40real-cookie-banner&new=3710645%40real-cookie-banner) is the referenced corrective commit, so administrators should update Real Cookie Banner to the first tagged release that incorporates it (i.e., a version strictly later than 5.3.5) and verify via the plugin changelog rather than assuming 5.3.5 or earlier is patched. Where updating is not immediately possible, the single most effective compensating control is to enforce human moderation of all comments (Settings > Discussion > 'Comment must be manually approved'), which directly removes the display step the exploit depends on - the trade-off is editorial workload and delayed community engagement, and it is not absolute since an approving moderator can still let a payload through. Additional hardening: disable comments on templates or pages where Real Cookie Banner is rendered (loses visitor interaction but eliminates the injection vector on those surfaces), require registered, pre-approved accounts to comment, and deploy a WAF rule or content filter that strips title attributes from anchor tags in submitted comment HTML - noting that such filtering can break legitimate links and is a partial mitigation because the underlying quote-delimiter bug in the plugin's renderer remains. Monitor the Wordfence advisory URL above for confirmation of the fixed release version before treating any specific release number as safe.

Affected VersionsENISA

Real Cookie Banner: GDPR & ePrivacy Cookie Consent 0 ≤5.3.5

Affected Packages

euvd real_cookie_banner_gdpr_eprivacy_cookie_consent no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The root cause is CWE-79, but the practical mechanism is a sanitizer/parser differential rather than a straightforward escaping bug. WordPress sanitizes comment content with kses, which permits a limited attribute set - including the title attribute on anchor tags - so a payload placed inside an anchor title survives the save-time filter as inert text. The plugin then re-parses that stored markup at render time through its bundled fast-html-tag library (FastHtmlTag.php, referenced at line 166) and its blocker/rendering logic (Blocker.php lines 213 and 233). That page-wide regex-based rewriting mishandles quote delimiters and can strip a closing quote, which changes the parsing context for the browser and promotes the previously inert title content into a live event or script-bearing attribute - the classic mXSS/context-shift pattern. CPE cpe:2.3:a:devowl:real_cookie_banner:_gdpr_&_eprivacy_cookie_consent:*:*:*:*:*:*:*:* confirms devowl as the affected vendor across the plugin's version line. Two independent trust boundaries are crossed (WordPress core sanitization assumptions versus the plugin's bespoke HTML rewriter), matching the S:C scope change, and the fact that the sanitizer says 'safe' while the downstream renderer says 'executable' is exactly why the base AC:L from the vendor understates the sequencing and moderation prerequisites.

Know when Real Cookie Banner gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (Wordfence) PRIMARY 7.2 HIGH
AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
vuln.today AI 5.4 MEDIUM

Unauthenticated remote injection (PR:N), but AC:H because exploitation depends on a specific render-time regex quirk plus passing comment moderation; S:C and C:L/I:L reflect script execution in visitors' browser context.

3.1 AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N
4.0 AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N

Primary rating from Vendor (Wordfence).

CVSS VectorVendor: Wordfence

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

DescriptionCVE.org

The Real Cookie Banner: GDPR & ePrivacy Cookie Consent plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Comment in all versions up to, and including, 5.3.5 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. Malicious script payloads placed in the title attribute of an anchor tag survive WordPress's comment kses filter at save time, as the payload is only promoted to executable HTML attributes when the plugin's page-wide regex strips the closing quote delimiter at render time; exploitability is therefore subject to the standard comment moderation workflow before the comment is publicly displayed.

Executive ViewAI

Why It Matters

The Real Cookie Banner: GDPR & ePrivacy Cookie Consent WordPress plugin (versions up to and including 5.3.5) contains a stored cross-site scripting vulnerability that allows unauthenticated commenters to inject malicious scripts, which execute when any visitor loads an affected page. This could compromise visitor browsers, leading to session hijacking, data theft, or site defacement, and may erode customer trust and trigger regulatory scrutiny. Although exploitation requires bypassing comment moderation and there is no public exploit identified at time of analysis, the absence of a vendor patch makes proactive mitigation critical.

Business Impact: High
Compensating Controls

Disable the Real Cookie Banner plugin until a patch is available; enforce strict comment moderation and disable unauthenticated commenting; deploy WAF rules to block XSS payloads targeting the plugin's render-time HTML rewriting; monitor comment submissions for malicious markup.

Threat Intelligence Overview

EPSS Score
0.2%
Top 86% exploitable
Prevalence
Medium
popular WordPress GDPR consent plugin, common but not universal
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.2%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Partial

Priority Score

36
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +36
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy