Skip to main content
WordPress plugin recordReviewed

Complianz vulnerability records, read beside the scripts it controls and the consent it can record

Once set up, Complianz shows a consent banner and holds back cookies and scripts until a visitor consents, its vendor says.

Beside each record's version fields, this page reads who holds manage_privacy, what sits in the "Script Center" and where consent records are kept.

Complianz vulnerability history

Source: Wordfence Intelligence (Vulnerability Data Feed v3, Production), retrieved on . It lists 25 records for Complianz. Copyright notices, licence terms and a link to each source record are under Data source and licence at the foot of this page.

Update to at least version 7.5.6

Worked out from data retrieved on .

Every affected range listed in this source for Complianz ends before version 7.5.6.

A vendor can publish a security release before this source records it. Read the plugin's own changelog as well as this history.

  1. Complianz GDPR/CCPA Cookie Consent Banner <= 7.5.5 - Unauthenticated Stored Cross-Site Scripting via Comment Content via yotu-wp Cookie-Blocker Filter

    Published:
    Last updated:
    Severity:
    High (CVSS 7.2)
    Affected versions
    • All versions up to and including 7.5.5

    Patched versions: 7.5.6

    Update to at least version 7.5.6.

  2. Complianz GDPR/CCPA Cookie Consent Banner <= 7.5.4 - Unauthenticated Stored Cross-Site Scripting via Elementor Cookie Blocker Regex

    Published:
    Last updated:
    Severity:
    High (CVSS 7.2)
    Affected versions
    • All versions up to and including 7.5.4

    Patched versions: 7.5.5

    Update to at least version 7.5.5.

  3. Complianz - GDPR/CCPA Cookie Consent <= 7.5.1 - Authenticated (Author+) Server-Side Request Forgery

    Published:
    Last updated:
    Severity:
    Medium (CVSS 6.4)
    Affected versions
    • All versions up to and including 7.5.1

    Patched versions: 7.5.2

    Update to at least version 7.5.2.

  4. Complianz - GDPR/CCPA Cookie Consent <= 7.5.1 - Authenticated (Administrator+) PHP Object Injection

    Published:
    Last updated:
    Severity:
    Medium (CVSS 6.6)
    Affected versions
    • All versions up to and including 7.5.1

    Patched versions: 7.5.2

    Update to at least version 7.5.2.

  5. Complianz - GDPR/CCPA Cookie Consent <= 7.5.1 - Unauthenticated Information Exposure

    Published:
    Last updated:
    Severity:
    Medium (CVSS 5.3)
    Affected versions
    • All versions up to and including 7.5.1

    Patched versions: 7.5.2

    Update to at least version 7.5.2.

Show 20 older records
  1. Complianz - GDPR/CCPA Cookie Consent <= 7.4.5 - Missing Authorization to Unauthenticated Private Post Content Disclosure via Consent Area REST Endpoint

    Published:
    Last updated:
    Severity:
    Medium (CVSS 5.3)
    Affected versions
    • All versions up to and including 7.4.5

    Patched versions: 7.4.6

    Update to at least version 7.4.6.

  2. Complianz - GDPR/CCPA Cookie Consent <= 7.4.4.2 - Authenticated (Contributor+) Stored Cross-Site Scripting via Content Filter

    Published:
    Last updated:
    Severity:
    Medium (CVSS 4.9)
    Affected versions
    • All versions up to and including 7.4.4.2

    Patched versions: 7.4.5

    Update to at least version 7.4.5.

  3. Complianz | GDPR/CCPA Cookie Consent <= 7.4.3 - Authenticated (Contributor+) Stored Cross-Site Scripting via Shortcode

    Published:
    Last updated:
    Severity:
    Medium (CVSS 6.4)
    Affected versions
    • All versions up to and including 7.4.3

    Patched versions: 7.4.4

    Update to at least version 7.4.4.

  4. Complianz - GDPR/CCPA Cookie Consent <= 6.5.6 - Cross-Site Request Forgery to Data Request Deletion

    Published:
    Last updated:
    Severity:
    Medium (CVSS 4.3)
    Affected versions
    • All versions up to and including 6.5.6

    Patched versions: 7.0.0

    Update to at least version 7.0.0.

  5. Complianz | GDPR/CCPA Cookie Consent <= 6.5.5 - Authenticated(Administrator+) Stored Cross-site Scripting via settings

    Published:
    Last updated:
    Severity:
    Medium (CVSS 4.4)
    Affected versions
    • All versions up to and including 6.5.5

    Patched versions: 6.5.6

    Update to at least version 6.5.6.

  6. Complianz <= 6.4.4 (Premium <= 6.4.6.1) - Cross-Site Request Forgery to Stored Cross-Site Scripting

    Published:
    Last updated:
    Severity:
    Medium (CVSS 6.1)
    Affected versions
    • All versions up to and including 6.4.4

    Patched versions: 6.4.5

    Update to at least version 6.4.5.

  7. Complianz <= 6.4.5 (Premium <= 6.4.7) - Cross-Site Request Forgery

    Published:
    Last updated:
    Severity:
    Medium (CVSS 4.3)
    Affected versions
    • All versions up to and including 6.4.5

    Patched versions: 6.4.6

    Update to at least version 6.4.6.

  8. Complianz | GDPR/CCPA Cookie Consent <= 6.4.5 - Cross-Site Request Forgery

    Published:
    Last updated:
    Severity:
    Medium (CVSS 4.3)
    Affected versions
    • All versions before 6.4.6

    Patched versions: 6.4.6

    Update to at least version 6.4.6.

  9. Complianz - GDPR/CCPA Cookie Consent <= 6.4.4 - Cross-Site Request Forgery via maybe_install_suggested_plugins

    Published:
    Last updated:
    Severity:
    Medium (CVSS 4.3)
    Affected versions
    • All versions up to and including 6.4.4

    Patched versions: 6.4.5

    Update to at least version 6.4.5.

  10. Complianz - GDPR/CCPA Cookie Consent <= 6.4.4 - Cross-Site Request Forgery via ajax_script_save

    Published:
    Last updated:
    Severity:
    Medium (CVSS 6.1)
    Affected versions
    • All versions up to and including 6.4.4

    Patched versions: 6.4.5

    Update to at least version 6.4.5.

  11. Complianz - GDPR/CCPA Cookie Consent <= 6.4.4 - Cross-Site Request Forgery via ajax_create_pages

    Published:
    Last updated:
    Severity:
    Medium (CVSS 4.3)
    Affected versions
    • All versions up to and including 6.4.4

    Patched versions: 6.4.5

    Update to at least version 6.4.5.

  12. Complianz - GDPR/CCPA Cookie Consent <= 6.4.4 - Cross-Site Request Forgery via ajax_edit_item

    Published:
    Last updated:
    Severity:
    Medium (CVSS 4.3)
    Affected versions
    • All versions up to and including 6.4.4

    Patched versions: 6.4.5

    Update to at least version 6.4.5.

  13. Complianz - GDPR/CCPA Cookie Consent <= 6.4.4 - Cross-Site Request Forgery via ajax_script_add

    Published:
    Last updated:
    Severity:
    Medium (CVSS 6.1)
    Affected versions
    • All versions up to and including 6.4.4

    Patched versions: 6.4.5

    Update to at least version 6.4.5.

  14. Complianz - GDPR/CCPA Cookie Consent <= 6.4.4 - Cross-Site Request Forgery via ajax_delete_snapshot

    Published:
    Last updated:
    Severity:
    Medium (CVSS 5.4)
    Affected versions
    • All versions up to and including 6.4.4

    Patched versions: 6.4.5

    Update to at least version 6.4.5.

  15. Complianz - GDPR/CCPA Cookie Consent <= 6.4.4 - Cross-Site Request Forgery via run_sync

    Published:
    Last updated:
    Severity:
    Medium (CVSS 4.3)
    Affected versions
    • All versions up to and including 6.4.4

    Patched versions: 6.4.5

    Update to at least version 6.4.5.

  16. Complianz - GDPR/CCPA Cookie Consent <= 6.4.4 - Cross-Site Request Forgery via cmplz_duplicate_cookiebanner

    Published:
    Last updated:
    Severity:
    Medium (CVSS 4.3)
    Affected versions
    • All versions up to and including 6.4.4

    Patched versions: 6.4.5

    Update to at least version 6.4.5.

  17. Complianz - GDPR/CCPA Cookie Consent <= 6.4.4 - Cross-Site Request Forgery via cmplz_delete_cookiebanner

    Published:
    Last updated:
    Severity:
    Medium (CVSS 4.3)
    Affected versions
    • All versions up to and including 6.4.4

    Patched versions: 6.4.5

    Update to at least version 6.4.5.

  18. Complianz - GDPR/CCPA Cookie Consent <= 6.4.1 - Authenticated (Contributor+) Stored Cross-Site Scripting

    Published:
    Last updated:
    Severity:
    Medium (CVSS 6.4)
    Affected versions
    • All versions up to and including 6.4.1

    Patched versions: 6.4.2

    Update to at least version 6.4.2.

  19. Complianz Free <= 6.3.3 & Premium <= 6.3.5 - SQL Injection via Translations

    Published:
    Last updated:
    Severity:
    High (CVSS 8.8)
    Affected versions
    • All versions up to and including 6.3.3

    Patched versions: 6.3.4

    Update to at least version 6.3.4.

  20. Complianz - GDPR/CCPA Cookie Consent <= 5.5.2 - Reflected Cross-Site Scripting via s parameter

    Published:
    Last updated:
    Severity:
    Medium (CVSS 6.1)
    Affected versions
    • All versions before 6.0.0

    Patched versions: 6.0.0

    Update to at least version 6.0.0.

Check Complianz on a live site

Read-only checks for a site you own or are authorised to review. Each step uses the WordPress dashboard or WP-CLI and sends no test payloads to the site.

Where Complianz takes input, and who reaches it

Complianz is a cookie consent plugin; its WordPress.org listing reads "By Complianz".

Its setup guide says Complianz does not show the banner until you turn it on in the wizard's last step, where Show Consent Banner and Enable cookie and script blocker are set to Yes before clicking Finish. When the guide's steps are done, it says, the consent banner is live and Complianz blocks cookies and scripts until visitors give consent.

Visitors meet it through the banner, and the listing names native Gutenberg blocks among its features. Behind the dashboard, the vendor's custom roles article says one capability, manage_privacy, controls access to the Dashboard, the Wizard and the settings. A third-party script can also be added in the "Script Center", whose article gives a Facebook Pixel as its example.

What the Complianz titles name, and where the history needs care

The history on this page holds the records the source data files under the slug complianz-gdpr.

The titles name the plugin in more than one way, so match a record by its CVE id, where it has one, and its fields. Stored cross-site scripting and cross-site request forgery recur, and access wording in the titles includes Unauthenticated, Authenticated (Contributor+), Authenticated (Author+) and Authenticated (Administrator+).

Some titles name a cookie blocker. CVE-2026-97339 has a title ending "Unauthenticated Stored Cross-Site Scripting via Comment Content via yotu-wp Cookie-Blocker Filter", an affected range of all versions up to and including 7.5.5, and 7.5.6 in its patched versions field. CVE-2026-83561, whose title ends "Unauthenticated Stored Cross-Site Scripting via Elementor Cookie Blocker Regex", covers all versions up to and including 7.5.4, with 7.5.5 as patched.

Not every title names a blocker: CVE-2026-4019 has a title ending "Unauthenticated Private Post Content Disclosure via Consent Area REST Endpoint", with all versions up to and including 7.4.5 affected and 7.4.6 patched.

Titles carrying CVE-2023-33333 include ones that differ only in their endings, such as "via ajax_script_save" and "via run_sync", and its fields read all versions up to and including 6.4.4, with 6.4.5 as patched. Titles ending "via cmplz_duplicate_cookiebanner" and "via cmplz_delete_cookiebanner", published on 12 May 2023, carry the same fields and no CVE id.

Some titles carry a Premium version too. The title of CVE-2022-3494 opens "Complianz Free <= 6.3.3 & Premium <= 6.3.5" and ends "SQL Injection via Translations", while its affected range is all versions up to and including 6.3.3, with 6.3.4 as patched.

The ranges in the history are those the source data files under the slug complianz-gdpr, so match the free plugin's version on the fields, not on a version in a title.

CVE-2024-1592 has a title ending "Cross-Site Request Forgery to Data Request Deletion". Its affected range is all versions up to and including 6.5.6, and its patched versions field lists 7.0.0. The fields say nothing about the versions between the two, so for that record the patched version is the one to reach.

The changelog on the WordPress.org listing has entries that begin with the word "Security", and the readme's upgrade notice reads "Please backup before upgrading."

Reading Complianz settings without saving anything

Each check reads a value and writes it down, on a site you own or have written permission to review.

The setup guide opens the wizard from Complianz → Dashboard with Continue Wizard; move between steps with Previous or the left menu, without pressing Save and Continue or Finish. If a Welcome to Complianz window asks for an email address, the guide says that after No, Thanks you can verify later from the Website Scan step.

Installed version and edition

Read the version in the Description column of the Plugins screen, with the date, and note whether the Premium plugin, whose file the setup guide names complianz-gdpr-premium, is installed. 1 min read

Regions and GEO IP

In the wizard's General section, the Visitors step holds the region choice; write down each region chosen and each follow-up answer. 1 min read

Consent categories and the blocker switch

The readme says Complianz sets up its consent settings from the wizard's answers and a scan, based on the site's plugins, services and region. 1 min read

Integrations and "Script Center" rules

The setup guide sends integration changes to Complianz → Integrations, and the vendor's article on the "Script Center" says it sits there. 1 min read

Consent records and who can open them

Records of Consent is a Premium feature that its article says is switched on under Complianz → Wizard → General → Security & Consent, after which individual consent records are stored in the database. 1 min read

What a Complianz version match leaves unanswered

Setting the installed Complianz version against the affected ranges shows which records it falls under.

It leaves open whether anyone used one against the site, who holds manage_privacy, what the "Script Center" adds to the site's pages, or whether the snapshots folder answers a request from outside.

A WordPress security audit goes past the version match. Its logged-out pass calls each REST route under /wp-json/ and each admin-ajax action that plugins register for logged-out visitors, with no session, and treats any that changes data, sends email or returns personal information or settings as a finding. It also checks for directory listings, the question the snapshots folder raises.

Frequently asked questions

This history imports only what the source data files under the slug complianz-gdpr, and that filing does not show whether a record also applies to Premium. The setup guide installs Premium by uploading the complianz-gdpr-premium file through Plugins → Add Plugin, and says you keep the settings from the free version. The vendor's Premium changelog numbers its releases its own way: its line on rate-limiting the public data request endpoint sits under a different number in the free changelog. A Premium version number is therefore not one to set against the ranges in the history. On a Premium site, read that changelog's entries that begin with the word "Security" alongside the update guidance at the top of the history.

Its 6.4.1 changelog entry says the plugin added its own manage_privacy capability because the WordPress core manage_privacy_options capability is not implemented consistently with other capabilities. The vendor's custom roles article says a role or user without manage_privacy cannot manage Complianz, and its examples grant it to one Editor or to every Editor.

The Records of Consent article lists a User ID kept in the visitor's browser in a cookie named cmplz_ID, an IP address Complianz anonymises before storing it, the region, the cookie categories chosen and a timestamp of the visitor's last choice. In place of categories it can record "No choice", when the banner was shown and not answered, or "No warning", when the consent process was cut off, for example by a Do Not Track or Global Privacy Control setting that Complianz respects.

Its readme says the plugin sends the results of its local or advanced website scan to cookiedatabase.org, operated by Complianz B.V., for cookie descriptions, and lists cookie names, the domain that provides them and the site's plugin list as collected for research. It says the advanced scan, authenticated with an email address, keeps public data from the site for one hour, then discards it. The listing's FAQ says no visitor data is sent to external servers.

Scope the right test for your application

Tell us what you have built, who uses it and when it needs to launch. You will get a plain-English recommendation: a website audit, a web application test or a referral to a specialist.

Data source and licence

The vulnerability records on this page come from Wordfence Intelligence (Vulnerability Data Feed v3, Production), retrieved on . The records contain material that is subject to copyright. Each copyright notice and its licence are reproduced once below, followed by a link to every source record.

Copyright 2012-2026 Defiant Inc.

Applies to every record listed below.

Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.

Copyright 1999-2026 The MITRE Corporation

Applies to 23 of the 25 records listed below.

CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.

Source records