Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-97339 Overview
CVE-2026-97339 is a Stored Cross-Site Scripting (XSS) vulnerability in the Complianz GDPR/CCPA Cookie Consent Banner plugin for WordPress. The flaw affects all versions up to and including 7.5.5. Unauthenticated attackers can inject arbitrary web scripts through comment content, which execute when visitors load an injected page. The exploit chain abuses the plugin's yotu-wp Cookie-Blocker filter, bypassing WordPress's wp_kses sanitization by hiding executable tokens inside allow-listed, quoted attribute values. Execution is triggered when Complianz's output-buffer filter performs str_replace() rewrites that break out of attribute context. Comments must be approved before the payload runs for visitors.
Critical Impact
Unauthenticated attackers can achieve stored script execution in visitor browsers on any WordPress site running Complianz with the yotu-wp integration path active.
Affected Products
- Complianz GDPR/CCPA Cookie Consent Banner plugin for WordPress
- All versions up to and including 7.5.5
- Sites using the yotu-wp Cookie-Blocker integration
Discovery Timeline
- 2026-10-16 - CVE-2026-97339 published to the National Vulnerability Database (NVD)
- 2026-10-16 - Last updated in NVD database
Technical Details for CVE-2026-97339
Vulnerability Analysis
The vulnerability is a stored XSS classified as [CWE-79]. The attack vector is network-based, requires no authentication, and no user interaction beyond visiting the affected page. The scope change in the CVSS vector reflects that script execution occurs in the browser of a different security context (site visitors) than the comment submission endpoint.
The payload persists in the WordPress comments table. It is only rendered maliciously after a site administrator approves the comment, which is a precondition for execution against visitors.
Root Cause
The root cause is insufficient input sanitization and output escaping in the Complianz Cookie-Blocker output pipeline, specifically within the yotu-wp integration file (integrations/plugins/yotu-wp.php) and the Cookie-Blocker class (class-cookie-blocker.php). WordPress's wp_kses filter does not strip the payload because it is composed of allow-listed HTML tags with executable tokens stored as plain text inside quoted attribute values. The Complianz output-buffer filter then applies str_replace() rewrites that alter the surrounding markup and break the attribute quoting, promoting the previously inert text into executable script context.
Attack Vector
An unauthenticated attacker submits a comment containing allow-listed HTML with carefully positioned attribute content. The comment passes wp_kses because every tag and attribute name is permitted. After administrator approval, any visitor who loads the page triggers the Complianz output-buffer filter. The str_replace() rewrite modifies attribute delimiters, closing the quoted context early and exposing attacker-controlled tokens as live HTML and script. See the Wordfence Vulnerability Analysis and the vulnerable source at WordPress Yotu WP Integration Code Line 18.
No verified public proof-of-concept code is available. See the referenced source files for technical details on the vulnerable rewrite logic.
Detection Methods for CVE-2026-97339
Indicators of Compromise
- Approved WordPress comments containing unusual combinations of allow-listed HTML tags with suspicious quoted attribute values referencing yotu, youtube, or iframe-like markup.
- Unexpected <script> or event-handler execution originating from /wp-content/plugins/complianz-gdpr/ asset paths.
- Browser console errors or Content Security Policy (CSP) violations tied to rendered comment regions on pages where Complianz output buffering is active.
Detection Strategies
- Audit the wp_comments table for approved comments containing attribute patterns targeting the yotu-wp integration, particularly markup that would be rewritten by Complianz str_replace() operations.
- Compare installed Complianz plugin versions against 7.5.5 across all WordPress properties and flag any at or below that version.
- Review web server access logs for comment POST requests from unauthenticated sources immediately followed by administrator approval activity.
Monitoring Recommendations
- Enable CSP reporting on WordPress front-end pages to capture script-source violations from injected comment content.
- Monitor WordPress admin workflows for bulk or atypical comment approvals, which are a precondition for exploitation.
- Alert on changes to plugin files under complianz-gdpr/integrations/plugins/ outside of patch windows.
How to Mitigate CVE-2026-97339
Immediate Actions Required
- Update the Complianz GDPR/CCPA Cookie Consent Banner plugin to a version newer than 7.5.5 that includes the fix shipped in WordPress Changeset #3743098.
- Review and unapprove or delete any suspicious pending or approved comments submitted while the vulnerable version was active.
- Require manual moderation for all comments until the plugin is patched and verified.
Patch Information
The vendor patch is delivered through WordPress Changeset #3743098, which modifies the yotu-wp integration to prevent the attribute-breaking rewrite. Operators should update through the WordPress plugin updater and confirm the installed version is greater than 7.5.5. Additional context is available in the Wordfence Vulnerability Analysis.
Workarounds
- Disable the Complianz yotu-wp integration if the Yotu WordPress plugin is not required on the site.
- Deactivate the Complianz plugin on sites that accept public comments until the update can be applied.
- Deploy a Web Application Firewall (WAF) rule to block comment submissions containing allow-listed HTML attribute patterns known to trigger the Cookie-Blocker rewrite.
# Configuration example: verify installed Complianz version via WP-CLI
wp plugin get complianz-gdpr --field=version
# Force update to the patched release
wp plugin update complianz-gdpr
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

