The CookieYes WordPress plugin before 3.5.8 does not correctly restrict who can write its cookie-category script
Source GCVE Database
Not known to be exploited : upgrade to 3.5.8 soon.
Data as of 4 Nov 2026, 07:43 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in 3.5.8
Exploitation evidence
Disclosed: evidence found.
CVE published 4 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 3 Nov 2026.
What to do
Upgrade CookieYes (WordPress plugin) to 3.5.8.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| CookieYes | Affected
| Fixed in
|
AI-suggested
Upgrade the CookieYes WordPress plugin to version 3.5.8 or later, where this vulnerability is fixed. Until then, restrict Contributor role permissions to prevent writing to cookie-category script fields or disable the plugin if possible. No vendor advisory or patch links are provided, so verify the availability of official fixes from the vendor.
Description
The CookieYes WordPress plugin versions prior to 3.5.8 have a vulnerability where users with the Contributor role can inject JavaScript into the cookie-category script fields. This occurs because the plugin does not properly restrict write access to these fields nor sanitize or escape the input, leading to potential cross-site scripting (XSS) attacks affecting site visitors and administrators reviewing content.