Unauthenticated stored XSS via unsanitized consent logs
Published Nov 6, 2025 · Updated Nov 6, 2025
Stored XSS in Christoph Rado Cookie Notice & Consent 1.6.4 and earlier allows remote attackers to inject scripts into WordPress pages. The consent-logging path stores attacker-controlled log data without sufficient sanitization, and affected views output persisted values without adequate escaping. Consent logging must be enabled, and execution occurs when a user opens an injected page, allowing script actions in that site's browser context.
Summary
What happened
Stored XSS in Christoph Rado Cookie Notice & Consent 1.6.4 and earlier allows remote attackers to inject scripts into WordPress pages. The consent-logging path stores attacker-controlled log data without sufficient sanitization, and affected views output persisted values without adequate escaping. Consent logging must be enabled, and execution occurs when a user opens an injected page, allowing script actions in that site's browser context.
The record
- CVE
- CVE-2025-49390
- Published
- Nov 6, 2025
- Updated
- Nov 6, 2025
- Vendor
- Christoph Rado
- Product
- Cookie Notice & Consent
- Classifications
- CWE-79, T1189
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 6, 2025CVE publishedPublication date reported by the CVE source.
- Nov 6, 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=n/a <=<= 1.6.4 changes=[{"at":"1.6.5","status":"unaffected"}]
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