WordPress plugin · Updated daily · Source: Wordfence Intelligence

Cookie Compliance for WordPress vulnerabilities: affected versions and fixes

Cookie Compliance for WordPress has 800,000+ active installs. Here are its publicly disclosed vulnerabilities, whether your version is affected, and what to do now.

Cookie Compliance for WordPress at a glance

  • 6 publicly disclosed vulnerabilities. The most recent was disclosed on Nov 21, 2025.
  • Ranked #75 by popularity on WordPress.org (800,000+ active installs).
  • The latest version is 3.1.20 (released Nov 20, 2026). The most recent security fix shipped in 2.5.9.
  • Every disclosed vulnerability has a fix. If you are on the latest version, none of them apply to you.
  • The first thing to do: update to the latest version and turn on automatic updates.

Check your Cookie Compliance for WordPress version

Enter the Cookie Compliance for WordPress version number shown on your Plugins screen to see only the vulnerabilities that apply to it, most serious first.

Your version number is compared on this page only. It is not sent anywhere.

Get an email when a new vulnerability is disclosed

We'll tell you when a new vulnerability is disclosed in “Cookie Compliance for WordPress”, with the version that fixes it. Free, email address only, stop any time.

We use your email address only for these alerts. Privacy policy

Want every plugin and theme on your site checked daily?

With Security Ready Standard, just install the “KazLinks Security Ready” plugin from WordPress.org. It sends only the names and versions of your plugins and themes, and we check them against disclosed vulnerabilities every day. Your first in-depth scan is free.

View the plugin on wordpress.orgGet a free in-depth scan

How to check whether your site is affected

  1. 1

    Find your version

    In your WordPress dashboard, open Plugins → Installed Plugins and look at the version number under “Cookie Compliance for WordPress”.

  2. 2

    Compare it with the list below

    If your version falls within “Affected versions”, that vulnerability applies to you. If you are on the “Fixed in” version or later, it does not.

  3. 3

    Update

    Click “Update now” to move to the latest version (3.1.20). Taking a backup first is a good idea.

  4. 4

    Turn on automatic updates

    On the same screen, click “Enable auto-updates” so future fixes are installed automatically.

Known Cookie Compliance for WordPress vulnerabilities

  • Cookie Notice & Compliance for GDPR / CCPA <= 2.5.8 - Authenticated (Contributor+) Stored Cross-Site Scripting via Shortcode

    Cross-site scripting (XSS) · CVE-2025-11186

    Affected versions: ≤ 2.5.8

    Fixed in: 2.5.9

    Severity: Medium 6.4 · Disclosed Nov 21, 2025

  • Cookie Notice & Compliance for GDPR / CCPA <= 2.5.8 - Authenticated (Author+) Stored Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2025-67554

    Affected versions: ≤ 2.5.8

    Fixed in: 2.5.9

    Severity: Medium 6.4 · Disclosed Oct 21, 2025

  • Cookie Notice & Compliance for GDPR / CCPA <= 2.4.17.1 - Authenticated (Admin+) Stored Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2022-3399

    Affected versions: ≤ 2.4.17.1

    Fixed in: 2.4.18

    Severity: Medium 4.4 · Disclosed Aug 15, 2024

  • Cookie Notice & Compliance for GDPR / CCPA <= 2.4.6 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'cookies_revoke_shortcode' Shortcode

    Cross-site scripting (XSS) · CVE-2023-0823

    Affected versions: ≤ 2.4.6

    Fixed in: 2.4.7

    Severity: Medium 6.4 · Disclosed Mar 6, 2023

  • Cookie Notice & Compliance for GDPR / CCPA <= 2.4.6 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'cookies_policy_link' Shortcodes

    Cross-site scripting (XSS) · CVE-2023-24400

    Affected versions: ≤ 2.4.6

    Fixed in: 2.4.7

    Severity: Medium 6.4 · Disclosed Mar 2, 2023

  • Cookie Notice & Compliance for GDPR / CCPA <= 2.1.1 - Authenticated (Admin+) Stored Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2021-24569

    Affected versions: < 2.1.2

    Fixed in: 2.1.2

    Severity: Medium 4.8 · Disclosed Aug 30, 2021

Vulnerability data: Wordfence Intelligence (Copyright Defiant, Inc. · license terms). Severity is the CVSS score (0–10). Most recent disclosure: Nov 21, 2025.

Most common weaknesses in Cookie Compliance for WordPress

Cross-site scripting (XSS)

6 issues

An attacker plants a malicious script on a page so that it runs in visitors’ browsers. If an administrator opens that page, the attacker can steal their session or act as the administrator.

Frequently asked questions

Is Cookie Compliance for WordPress safe to use?

Cookie Compliance for WordPress is a well-known plugin with 800,000+ active installs. Finding vulnerabilities in popular plugins is common, and most of them are fixed in newer versions. The important thing is to stay on the latest version (3.1.20) and turn on automatic updates.

How do I find which version of Cookie Compliance for WordPress my site is running?

In your WordPress dashboard, go to Plugins → Installed Plugins. The version number is shown under the plugin name. If you see “There is a new version available”, you are on an older version.

Could updating break my site?

Occasionally an update changes how something looks or works, so take a backup before updating. If an agency or developer maintains your site, send them a link to this page and ask them to update.

Can I check all my other plugins too?

Yes. Security Ready reads the versions of every plugin and theme on your site, matches them against known vulnerabilities every day, and tells you what to fix. Your first in-depth scan is free.

Check every plugin and theme automatically, every day

Security Ready reads the versions of every plugin, theme and WordPress core on your site, matches them against known vulnerabilities every day, and tells you how to fix what it finds. Your first in-depth scan is free, and no payment details are needed.

Think your site has already been hacked? Before updating, read what to do in the first hour. Updating alone does not remove a backdoor that has already been planted.

← All plugin vulnerabilitiesCookie Compliance for WordPress on WordPress.org