CSS What Project maintains a narrowly scoped CSS selector parsing library that, despite a small product footprint, sits upstream in web-development toolchains and templating systems where selector validation is required. The observed vulnerability surface has centered on the parsing and validation logic inherent to selector interpretation, reflecting the complexity of CSS grammar handling. Current severity, exploitation, and exposure counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Css What Project over time
Signals from CVEs in this vendor scope (2 CVEs).
2 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2022-21222HIGH The package css-what before 2.1.3 are vulnerable to Regular Expression Denial of Service (ReDoS) due to the usage of insecure regular expression in the re_attr variable of index.js | Sep 30, 2022 | 7.5 | 25 | NO | NO |
CVE-2021-33587HIGH The css-what package 4.0.0 through 5.0.0 for Node.js does not ensure that attribute parsing has Linear Time Complexity relative to the size of the input. | May 28, 2021 | 7.5 | 25 | NO | NO |
Signals from CVEs in this vendor scope (2 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Css What Project.
Media articles that mention a CVE ID that affects a product developed by Css What Project — matched by CVE ID, not by vendor name.