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.
On this page
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.
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)
- CVE:
- CVE-2026-104719
Affected versions- All versions before 3.5.8
Patched versions: 3.5.8
Update to at least version 3.5.8.
GDPR Cookie Consent & Compliance Notice <= 1.8.2 - Authenticated Stored Cross-Site Scripting and Authorization Bypass
- Published:
- Last updated:
- Severity:
- Medium (CVSS 6.4)
- CVE:
- CVE-2020-20633
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.
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.
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. Then note which interface the site runs. On a legacy site, the legacy setup guide puts the settings under WordPress admin > "GDPR Cookie Consent" > Settings, and the migration guide's update steps start from "GDPR Cookie Consent" > "Review & update".
After an update to the new interface, the migration guide's rollback steps start from WordPress Dashboard > CookieYes Dashboard.
Last, record whether the site is connected to the CookieYes web app. The setup guide says that after connecting an existing account you are taken back to the CookieYes section within WordPress, displaying the success message "Your website is connected to the CookieYes web app". A vendor FAQ says the legacy version connects to the web app solely for scanning purposes.
Without a web app connection, the setup guide puts the banner settings under WordPress admin > CookieYes > Dashboard > Cookie Banner. On its General tab, write down the "Consent Template" chosen, "Reload page on consent action" and "Consent Expiration (days)".
On a connected site, the listing says the banner is served and managed from the web app, and the setup guide reaches its banner settings through Dashboard > Go to the Web App; read them there only if you hold a login.
The Team Member Permissions page gives the web app's Editor role "Customise cookie banner" and "Manage Banner Display status" by default.
On the legacy General tab, under "GDPR Cookie Consent" > Settings, record "Enable cookie bar", which the legacy guide says enables or disables the display of the cookie bar on the front end and is on by default, and whether "Auto-hide(Accept) cookie bar after delay?" or "Auto-hide cookie bar if the user scrolls (Accept on Scroll)?" is set to Yes.
The guide says the first, if enabled and configured, lets you set a time limit to assume user acceptance if they remain on the webpage that long, and the second allows automatic acceptance of the cookie bar when the user scrolls through the webpage.
Without a web app connection, the same General tab also holds "Load cookies prior to consent" and "Hide categories from banner". The setup guide says selecting a category under the first makes cookies in that category load before receiving user consent, and selecting one under the second hides it from the cookie banner.
Write down any selected. On a legacy site, the legacy guide keeps categories under "GDPR Cookie Consent" > Cookie Category: note each category's "Category default state", which it says sets the category toggle to active when enabled.
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.
For each cookie, write down its category and any script URL pattern. The setup guide's steps open an existing cookie with the edit icon and save it with "Submit", so close it without pressing "Submit". The listing adds that if another plugin sets cookies outside CookieYes, the vendor cannot control that.
On a legacy site, copy each category's Head Scripts and Body Scripts fields, leaving without pressing "Update", then read the Script Blocker list. The legacy guide names the plugins it supports, Official Facebook Pixel, Smash Balloon Instagram Feed, Smash Balloon Twitter Feed and Google Analytics for WordPress by MonsterInsights, and says they are enabled by default to be blocked on the front end until user consent is obtained, with a toggle next to each to disable automatic script blocking. Record which toggles are on.
The listing says consent logs need a connection to the CookieYes web app. Two vendor pages word the switch differently: the setup guide says to toggle the Enable consent log on and off at CookieYes Dashboard > Advanced Settings, and the consent log FAQ gives a toggle labelled "Consent log" under Consent Settings in the Advanced Settings. Write down whether it is on.
Then list who can manage the log in the web app. The Team Member Permissions page gives the Editor role "Manage Consent Log" and "Download proof of consent" by default, and gives Admin and Account Owner everything an Editor has, and more.
It says a team member's permissions can only be modified by the Account Owner or an Admin, from Team under the Profile icon in the top-right corner of the CookieYes Dashboard. Ask one of them for each team member's role.
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 licenceHide the 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.
Source records
- CookieYes - Cookie Banner for Cookie Consent (Easy to setup GDPR/CCPA Compliant Cookie Notice) < 3.5.8 - Authenticated (Contributor+) Stored Cross-Site Scripting (CVE-2026-104719)
- GDPR Cookie Consent & Compliance Notice <= 1.8.2 - Authenticated Stored Cross-Site Scripting and Authorization Bypass (CVE-2020-20633)