CVE-2026-97339

7.2High

Published 16 Oct 2026 · NVD status: Deferred · AI triage by gemini-3.8-flash

7.2High

Attack vector: Network
Complexity: Low
Privileges needed: None
User interaction: None
Impact: Limited impact
Weakness: CWE-79

Impact

Unauthenticated attackers can inject persistent malicious scripts into comment sections that run in visitors' browsers. Attackers need network access to submit a comment and require the comment to be approved.

Root cause

The plugin's output-buffer filter performs unsafe str_replace() rewrites on comment HTML that break attribute quoting and unmask hidden script payloads.

Affected systems

Complianz GDPR/CCPA Cookie Consent Banner for WordPress through 7.5.5

CVSS v3.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N

Fix & remediation

Upgrade Complianz GDPR/CCPA Cookie Consent Banner to a version newer than 7.5.5. As an interim workaround, disable the yotu-wp integration or deactivate the plugin.

shell

$ wp plugin update complianz-gdpr

AI-suggested. Run it in staging first and check it against the vendor advisory. Why?

Ad · In-content banner

NVD description

The Complianz GDPR/CCPA Cookie Consent Banner plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Comment Content via yotu-wp Cookie-Blocker Filter in all versions up to, and including, 7.5.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. The exploit bypasses WordPress's wp_kses comment sanitization because the payload uses only allow-listed tags and hides executable tokens inside quoted attribute values as plain text; the XSS is only realized when Complianz's own output-buffer filter performs str_replace() rewrites that break out of the attribute context, and requires the comment to be approved before it executes for visitors.

References

Source: nvd.nist.gov/vuln/detail/CVE-2026-97339