What is the CVSS score of EUVD-2026-16175?

EUVD-2026-16175 has a CVSS 3.1 base score of 4.9 (Medium). CVSS vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:N. EPSS exploitation probability: 0.0%.

Which versions of WordPress are affected by EUVD-2026-16175?

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.. A patch is available.

How to fix or mitigate EUVD-2026-16175?

Within 30 days: Identify affected systems running for WordPress is vulnerable to Stored Cross-Site Scripting i and apply vendor patches as part of regular patch cycle. Verify Content-Security-Policy and output encoding.

WordPress EUVD-2026-16175

| CVE-2026-2389 MEDIUM

Cross-site Scripting (XSS) (CWE-79)

2026-03-26 Wordfence

GHSA-mp6q-xf9x-fwf7

WordPress XSS

4.9

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

4.9 MEDIUM

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

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:N

Attack Vector

Network

Attack Complexity

High

Privileges Required

Low

User Interaction

None

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

None

Lifecycle Timeline

Patch released

Mar 31, 2026 - 21:13 nvd

Patch available

EUVD ID Assigned

Mar 26, 2026 - 13:45 euvd

EUVD-2026-16175

Analysis Generated

Mar 26, 2026 - 13:45 vuln.today

CVE Published

Mar 26, 2026 - 13:26 nvd

MEDIUM 4.9

DescriptionCVE.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.

AnalysisAI

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.

Technical ContextAI

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.

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.