Skip to main content
WordPress plugin recordReviewed

CookieYes vulnerability records, read against its legacy and new settings

Records filed under CookieYes include CVE-2026-104719, whose title ends "Authenticated (Contributor+) Stored Cross-Site Scripting".

A site may run the plugin's legacy settings screens or its newer ones, so the checks start there, then read the banner, categories, blocked scripts and consent log.

CookieYes vulnerability history

Source: Wordfence Intelligence (Vulnerability Data Feed v3, Production), retrieved on . It lists 2 records for CookieYes. 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 3.5.8

Worked out from data retrieved on .

Every affected range listed in this source for CookieYes ends before version 3.5.8.

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

  1. CookieYes - Cookie Banner for Cookie Consent (Easy to setup GDPR/CCPA Compliant Cookie Notice) < 3.5.8 - Authenticated (Contributor+) Stored Cross-Site Scripting

    Published:
    Last updated:
    Severity:
    Medium (CVSS 6.4)
    Affected versions
    • All versions before 3.5.8

    Patched versions: 3.5.8

    Update to at least version 3.5.8.

  2. GDPR Cookie Consent & Compliance Notice <= 1.8.2 - Authenticated Stored Cross-Site Scripting and Authorization Bypass

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

    Patched versions: 1.8.3

    Update to at least version 1.8.3.

Check CookieYes 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.

What CookieYes runs, and where its settings live

CookieYes's WordPress.org listing says a consent banner appears as soon as you activate the plugin, and that the plugin is free and works without an account.

Once the plugin is connected to the CookieYes web app, the listing says, "your banner is then served and managed from the web app", and the plugin connects the site to app.cookieyes.com to run cookie scans, sync settings with the CookieYes account and show scan results and consent data in its dashboard.

In WordPress, the settings sit in one of two sets of screens. The vendor's FAQ says CookieYes introduced plugin v3.0.0, with a redesigned interface, on 26 September 2022, and that a site with the legacy interface, installed before that date, keeps the same design even after updating to version 3.0.0 or above.

The legacy screens take more than text. The legacy setup guide says the cookie bar's "Message" field accepts basic HTML tags and other shortcodes. It gives each cookie category a Head Scripts field, whose scripts are rendered in the head of the website upon user consent, and a Body Scripts field, whose scripts are rendered in the body of the website.

CookieYes security records under more than one product name

CVE-2026-104719 has a title ending "Authenticated (Contributor+) Stored Cross-Site Scripting", and the source data rates it Medium (CVSS 6.4).

Its affected range and patched versions field read all versions before 3.5.8, with 3.5.8 patched.

CVE-2020-20633 has a title that opens with a different product name. The source data also rates it Medium (CVSS 6.4), with all versions up to and including 1.8.2 affected and 1.8.3 patched. Both records named here are filed under the cookie-law-info slug, so match each on its version fields, whatever name its title opens with.

The range of CVE-2026-104719, all versions before 3.5.8, takes in 1.8.3, the patched version for CVE-2020-20633, so reaching one record's patched version can leave a site inside another record's range. Set the installed version against each range in the history on this page, then read the update guidance at the top of the history.

The changelog on CookieYes's WordPress.org listing has entries that begin "Security: On sites using the legacy settings", one of them going on "users below Administrator could add scripts to cookie categories. Managing category scripts is now limited to administrators." Read those entries beside the update guidance at the top of the history.

Reading a CookieYes site without changing it

Every check here is a reading, on a site you are authorised to review, and nothing is saved.

The legacy setup guide says "Delete settings and reset" will restore the plugin to its default state, removing all customised settings, in an action it calls irreversible, and that "Delete site data from CookieYes" will delete all your data from the CookieYes account.

Leave both alone, and the migration guide's "Switch back to old UI" too. Where the consent log is on, the consent log FAQ says it will record all user consents given via the banner on the website. Leave the live banner unanswered.

Plugin version, interface and connection

WordPress's documentation for the Plugins screen lists each plugin's version in its Description column: write down the one shown for CookieYes, with any update notice. 1 min read

Banner state

Without a web app connection, the setup guide puts the banner settings under WordPress admin > CookieYes > Dashboard > Cookie Banner. 1 min read

Consent categories

Without a web app connection, the same General tab also holds "Load cookies prior to consent" and "Hide categories from banner". 1 min read

Script blocking

Without a web app connection, the setup guide keeps cookies under CookieYes > Dashboard > Cookie Manager > Cookie List, and among the fields it gives a cookie added there are its category and "Script URL Pattern", where you "Enter a valid script URL pattern to block third-party scripts from setting cookies." The migration guide places that field under Add Cookie > Advanced Settings. 1 min read

Consent log access

The listing says consent logs need a connection to the CookieYes web app. 1 min read

What a CookieYes version match leaves open

A CookieYes version inside a record's range ties the site to a known record, not to any attack on it.

The vendor's FAQ says a site with the legacy interface keeps it even after updating to version 3.0.0 or above, so from that version on the number cannot show which interface the site runs. No version shows what sits in a legacy category's script fields, which categories are selected under "Load cookies prior to consent", or who in the web app team can download proof of consent.

For a plugin whose records name stored cross-site scripting and whose legacy settings hold scripts, the parts of a WordPress security audit that fit are replaying requests an administrator makes in plugin settings screens as a subscriber, confirming that editors cannot reach settings requests by calling them directly, and checking whether script an editor saves runs when an administrator opens the page.

Frequently asked questions

The CookieYes listing on WordPress.org sits at the slug cookie-law-info, and the history on this page holds the records the source data files under that slug, among them CVE-2020-20633, whose title opens with a different product name. The vendor's migration guide names CookieLawInfoConsent among the older version plugin cookies to remove from the cookie list after migration to the new interface.

Only entries filed under the cookie-law-info slug come into this history, and that filing cannot show whether a record bears on a paid plan. The listing describes Basic, Pro and Ultimate as paid web app plans, and says that when you connect the plugin to the web app, "the features available follow your web app plan".

With a web app connection, the listing says consent logs are stored in EU-based data centres, and that the plugin itself sets a single cookie, "cookieyes-consent", to remember each visitor's choices in their browser. The consent log FAQ says the information recorded includes the Consent ID, Consent Status and Proof of Consent. The setup guide says the log can be downloaded with an "Export as CSV" button. Ask who has exported it.

The listing says a connected banner is served and managed from the web app, and the setup guide says that after logging in to connect an existing account, you can keep the current configurations or replace them with plugin settings. Connecting would change where the banner comes from, so read the connection state instead, and leave the "Connect to Web App" and "Connect Your Existing Account" buttons alone.

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 every record 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.