CVE-2026-2389
Received Received - Intake
Stored XSS in Complianz GDPR Plugin via revert_divs_to_summary Function

Publication date: 2026-03-26

Last updated on: 2026-03-26

Assigner: Wordfence

Description
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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-03-26
Last Modified
2026-03-26
Generated
2026-05-27
AI Q&A
2026-03-26
EPSS Evaluated
2026-05-25
NVD
EUVD
Affected Vendors & Products
Showing 4 associated CPEs
Vendor Product Version / Range
wpbeaverbuilder complianz_gdpr_ccpa_cookie_consent to 7.4.4.2 (inc)
wordpress classic_editor *
complianz gdpr_ccpa_cookie_consent to 7.4.4.2 (inc)
complianz gdpr_ccpa_cookie_consent From 7.4.5 (inc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-79 The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.
Attack-Flow Graph
AI Powered Q&A
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

The vulnerability in the Complianz – GDPR/CCPA Cookie Consent plugin allows authenticated attackers with Contributor-level access and above to inject arbitrary scripts via Stored Cross-Site Scripting (XSS). This can lead to unauthorized script execution on pages that users access.

Since the plugin is designed to help websites comply with privacy regulations such as GDPR and CCPA by managing cookie consent and related legal documents, the presence of this vulnerability undermines the integrity and security of the consent mechanism.

Exploitation of this vulnerability could result in unauthorized data access or manipulation, potentially violating data protection principles required by standards like GDPR and HIPAA, which mandate secure handling of personal data and protection against unauthorized access.

Therefore, until the vulnerability is patched (fixed in version 7.4.5), affected sites may be at increased risk of non-compliance due to security weaknesses in their consent management system.


How can this vulnerability be detected on my network or system? Can you suggest some commands?

This vulnerability is a Stored Cross-Site Scripting (XSS) issue in the Complianz – GDPR/CCPA Cookie Consent WordPress plugin versions up to 7.4.4.2. Detection involves identifying if your WordPress installation uses this plugin version along with the Classic Editor plugin, and if there is any injected script in post content that could be exploited.

To detect the vulnerability on your system, you can check the installed plugin version and look for suspicious script injections in posts or pages edited by users with Contributor-level access or higher.

  • Check the Complianz plugin version installed on your WordPress site. You can do this via WP-CLI with the command: wp plugin list | grep complianz
  • Check if the Classic Editor plugin is installed and active: wp plugin list | grep classic-editor
  • Search for suspicious script tags or encoded double-quote entities (&amp;#8221;) replaced by literal quotes in post content. For example, you can query the WordPress database posts table for suspicious content using SQL: SELECT ID, post_title FROM wp_posts WHERE post_content LIKE '%<script%' OR post_content LIKE '%&quot;%';
  • Monitor HTTP traffic for reflected or stored XSS payloads by capturing requests and responses to pages that use the Complianz plugin's shortcodes or blocks.

Note that no specific detection commands or signatures are provided in the available resources, so detection relies on version checking and manual or automated inspection of post content for injected scripts.


How can this vulnerability impact me? :

This Stored Cross-Site Scripting vulnerability can allow attackers with Contributor-level access to inject malicious scripts into website pages.

When other users visit these pages, the injected scripts can execute in their browsers, potentially leading to theft of sensitive information, session hijacking, or unauthorized actions performed on behalf of users.

Because the vulnerability requires authenticated access, it primarily impacts sites where users have Contributor or higher privileges.


What immediate steps should I take to mitigate this vulnerability?

To mitigate the Stored Cross-Site Scripting vulnerability in the Complianz – GDPR/CCPA Cookie Consent plugin for WordPress, you should immediately update the plugin to version 7.4.5 or later, where the vulnerability has been fixed.

Ensure that the Classic Editor plugin is either removed or properly secured, as it is required to exploit this vulnerability.

Limit Contributor-level and higher access to trusted users only, since authenticated attackers with Contributor-level access can exploit this issue.

Review and sanitize any post content that may have been injected with malicious scripts due to this vulnerability.


Can you explain this vulnerability to me?

The vulnerability in the Complianz – GDPR/CCPA Cookie Consent plugin for WordPress is a Stored Cross-Site Scripting (XSS) issue present in all versions up to and including 7.4.4.2.

It occurs because the function `revert_divs_to_summary` replaces certain HTML entities (`&amp;#8221;`) with literal double-quote characters (`&quot;`) in post content without properly sanitizing the input afterward.

This flaw allows authenticated attackers with Contributor-level access or higher to inject arbitrary web scripts into pages. These scripts execute whenever any user accesses the compromised page.

Exploitation requires the Classic Editor plugin to be installed and activated.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart