Skip to content
Fencer Intel
medium 5.4

CVE-2026-119177 json

Real Cookie Banner: GDPR & ePrivacy Cookie Consent <= 5.4.2 - Unauthenticated Stored Cross-Site Scripting via Comment Content via Regex Boundary Consumption

published 16h ago modified 15h ago also EUVD-2026-132123

cvss
5.4
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
—
no EPSS score yet
public exploits
0
none known

Summary

The Real Cookie Banner: GDPR & ePrivacy Cookie Consent plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'comment' parameter in all versions up to, and including, 5.4.2 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. Exploitation requires that the cookie banner has been activated by the site administrator (the plugin's primary onboarding step) and that at least one prior comment from the same name and email identity has already been approved, after which WordPress core's comment_previously_approved default auto-approves subsequent comments without administrator action.

Is CVE-2026-119177 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CVSS scores

assigned by version score vector
CNA 3.1 5.4 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N
NVD 3.1 5.4 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N

Affected products

  • devowl Real Cookie Banner: GDPR & ePrivacy Cookie Consent

Classification

Weakness
  • CWE-79 Improper Neutralization of Input During Web Page Generation
Technology feeds

References

Sources

Fencer Intel 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.