CVE-2025-71310: BackdropCMS GDPR cookies module for Backdrop CMS · Basic XSS
Affects BackdropCMS GDPR cookies module for Backdrop CMSSource CVE Database V5
Not known to be exploited · CVSS 1.8 Low : upgrade to 1.x-1.3.5 when convenient.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 18% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.x-1.3.5
CVSS:4.0/AV:N/AC:H/AT:P/PR:H/UI:A/VC:N/VI:N/VA:N/SC:N/SI:L/SA:LExploitation evidence
Disclosed: evidence found.
CVE published 26 May 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 30 Oct 2026.
What to do
Upgrade BackdropCMS GDPR cookies module for Backdrop CMS to 1.x-1.3.5.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| BackdropCMSGDPR cookies module for Backdrop CMS | Affected
| Fixed in
|
GitHubGDPR cookies module for Backdrop CMSpkg:github/GDPR cookies module for Backdrop CMSOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
If you cannot patch yet, restrict permissions to only trusted users for 'Create a GDPR Cookies Service' and 'Edit any GDPR Cookies Service' roles. Review and validate any configured YouTube service info content to prevent injection of malicious scripts.
Description
The GDPR cookies module for Backdrop CMS (before 1.x-1.3.5) doesn't sufficiently protect visitors from Cross Site Scripting (XSS) if a malicious value has been provided for the optional 'Info content' field for the YouTube service. This is mitigated by the fact that an attacker must have a role with the permission "Create a GDPR Cookies Service" or "Edit any GDPR Cookies Service" and a site must have added a YouTube service as configuration.