EUVD-2026-16175
GHSA-mp6q-xf9x-fwf7
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. |
| Impact | CVSS 3.1 score of 4.9 reflects low-to-moderate severity with a vector indicating network-accessible attack (AV:N), high complexity (AC:H), low privilege requirements (PR:L), no user interaction (UI:N), and changed scope (S:C) with limited confidentiality and integrity impact (C:L/I:L). The SSVC decision framework categorizes exploitation status as none, automatable as no, and technical impact as partial-suggesting this is not actively exploited at scale and requires manual attack crafting. While stored XSS typically poses significant risk, the authentication barrier (Contributor role minimum), editor plugin dependency, and lack of automated exploitation potential substantially reduce real-world attack surface. Organizations with strict contributor access controls or those not using Classic Editor face minimal risk. The AC:H (high complexity) rating indicates successful exploitation requires specific conditions or user behavior, further limiting priority compared to high-CVSS unauthenticated flaws. |
| Exploit ScenarioDerived | An authenticated attacker with Contributor access (e.g., a disgruntled employee or compromised low-privilege account) crafts a WordPress post or page containing specially-formed content that exploits the character entity conversion flaw. When the post is saved using Classic Editor, the |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Mar 26, 2026
Stored Cross-Site Scripting in Complianz - GDPR/CCPA Cookie Consent plugin versions up to 7.4.4.2 allows authenticated attackers with Contributor-level access to inject arbitrary JavaScript into WordPress pages via the revert_divs_to_summary function, which improperly converts HTML entities to unescaped characters without subsequent sanitization. The vulnerability requires both the Classic Editor plugin and authenticated user privileges, limiting exposure to internal threats. No public exploit identified at time of analysis, and CISA KEV status is not confirmed.
RemediationAI
Upgrade Complianz - GDPR/CCPA Cookie Consent plugin to a version released after 7.4.4.2. The plugin repository changeset reference (https://plugins.trac.wordpress.org/changeset/3483618/) indicates fixes are available in trunk; users should update to the latest stable release when made available. As an interim mitigation for organizations unable to immediately patch, restrict Contributor-level and above user account creation to trusted administrators, audit existing contributor and editor accounts for suspicious activity, and consider disabling Classic Editor if compatibility with modern block editor is feasible, since the vulnerability is not exploitable without it. Monitor post and page revisions for injected script content, particularly those edited by recently-added or untrusted contributors.
Affected VersionsENISA
Affected Packages
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 vulnerability exists in the Complianz plugin (CPE: cpe:2.3:a:complianz:complianz_-_gdpr/ccpa_cookie_consent:*:*:*:*:*:*:*:*) and stems from improper output encoding in the revert_divs_to_summary function located in the class-document.php file. The root cause is classified as CWE-79 (Improper Neutralization of Input During Web Page Generation), a Stored XSS variant. The function replaces HTML entity ” (right double quotation mark) with literal double-quote characters without applying subsequent HTML escaping or sanitization filters. This allows attackers to break out of HTML contexts and inject script tags that persist in post content. The dependency on Classic Editor plugin indicates the vulnerability is exploitable through the legacy WordPress editor interface.
Know when Complianz 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
AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:N
Primary rating from NVD · only source for this CVE.
CVSS VectorNVD
Lifecycle Timeline
2DescriptionCVE.org
The Complianz - GDPR/CCPA Cookie Consent plugin for WordPress is vulnerable to Stored Cross-Site Scripting in all versions up to, and including, 7.4.4.2. This is due to the revert_divs_to_summary function replacing ” HTML entities with literal double-quote characters (") in post content without subsequent sanitization. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses the injected page. The Classic Editor plugin is required to be installed and activated in order to exploit this vulnerability.
Executive ViewAI
Organizations using for WordPress is vulnerable to Stored Cross-Site Scripting in all should be aware of moderate risk from CVE-2026-2389, a cross-site scripting vulnerability rated CVSS 4.9. Attackers could inject scripts to steal sessions or perform actions as authenticated users. Organizations should apply vendor updates when available and monitor for exploitation.
Apply vendor patch. If patching is delayed: implement CSP headers, enable HttpOnly cookies, deploy WAF XSS rules.
Threat Intelligence Overview
NVD
CVE.org
EPSS
Vulnrichment
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
Related Vulnerabilities in XSS Vulnerabilities in Web Applications
View all 6The Complianz WordPress plugin before 6.3.4, and Complianz Premium WordPress plugin before 6.3.6 allow a translators to
The Complianz WordPress plugin before 6.4.2, Complianz Premium WordPress plugin before 6.4.2 do not validate and escape
PHP Object Injection in the Complianz WordPress plugin (all versions up to and including 7.5.0) allows an authenticated
Stored cross-site scripting in the Complianz GDPR/CCPA Cookie Consent Banner plugin for WordPress (all versions up to an
Stored cross-site scripting in the Complianz GDPR/CCPA Cookie Consent Banner WordPress plugin, affecting all versions up
Cross-Site Request Forgery (CSRF) vulnerability in Really Simple Plugins Complianz, Really Simple Plugins Complianz Prem
Cross-Site Request Forgery (CSRF) vulnerability in Really Simple Plugins Complianz, Really Simple Plugins Complianz Prem
Unauthenticated sensitive data exposure in the Complianz WordPress plugin (versions up to and including 7.5.0) allows an
Server-Side Request Forgery in the Complianz WordPress GDPR compliance plugin (versions 7.5.0 and below) allows authenti
The Complianz - GDPR/CCPA Cookie Consent plugin for WordPress is vulnerable to Stored Cross-Site Scripting via admin set
The Complianz - GDPR/CCPA Cookie Consent plugin for WordPress is vulnerable to Cross-Site Request Forgery in all version
Exploit-DB