Unauthenticated stored XSS via unsanitized consent UUID
Published Oct 9, 2025 · Updated Oct 9, 2025
Stored XSS in Cookie Notice & Consent 1.6.5 and earlier allows remote attackers to inject scripts through the uuid parameter. The consent logger stores the attacker-controlled UUID in consent-log data without sanitizing it, and administrative log views render that value without output escaping. No authentication is required to submit the value; the stored payload executes in the site's origin when the affected consent-log view is rendered.
Summary
What happened
Stored XSS in Cookie Notice & Consent 1.6.5 and earlier allows remote attackers to inject scripts through the uuid parameter. The consent logger stores the attacker-controlled UUID in consent-log data without sanitizing it, and administrative log views render that value without output escaping. No authentication is required to submit the value; the stored payload executes in the site's origin when the affected consent-log view is rendered.
The record
- CVE
- CVE-2025-10496
- Published
- Oct 9, 2025
- Updated
- Oct 9, 2025
- Vendor
- Christoph Rado
- Product
- Cookie Notice & Consent
- Classifications
- CWE-80, T1059.007
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 9, 2025CVE publishedPublication date reported by the CVE source.
- Oct 9, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=* <=1.6.5
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo