CVE-2025-1781: There is a XXE in W3CSS Validator versions before cssval-20250226 that allows an attacker to use specially-cra
CVE-2025-1781 is a medium-severity flaw (CVSS 6.5) affecting css validator. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
There is a XXE in W3CSS Validator versions before cssval-20250226 that allows an attacker to use specially-crafted XML objects to coerce server-side request forgery (SSRF). This could be exploited to read arbitrary local files if an attacker has access to exception messages.
Why this priority
- Public exploit reference
A fixed release or distro patch exists.
Risk facts
| CVSS score | 6.5 (Medium) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | Low |
| User interaction | None |
| EPSS exploit chance | 0.4% (top 67%) |
| CISA exploited list | No |
| Weakness | CWE-611 |
| Published | 2025-03-28 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2025-1781?
css validator: upgrade to 20250226. Exact commands for each OS are on this page.
Is CVE-2025-1781 being exploited?
CVE-2025-1781 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2025-1781 affect?
CVE-2025-1781 affects css validator. Severity is medium (CVSS 6.5). There is a XXE in W3CSS Validator versions before cssval-20250226 that allows an attacker to use specially-crafted XML objects to coerce server-side request forgery (SSRF). This could be exploited to read arbitrary local files if an attack
How urgent is CVE-2025-1781?
Priority 36/100. Public exploit reference