Chainnpm:sanitize-html
sanitize-html: successive fixes (2016–2024)
4 CVEs over 4 generations, 23 Jan 2020 to 24 Feb 2024.
Family tree
Left to right by publication date.Oldest first. Select a CVE to open it.- CVE-2016-100023723 Jan 2020 First in the chain
- CVE-2021-265398 Feb 2021 related to CVE-2016-1000237
- CVE-2022-2588730 Aug 2022 related to CVE-2016-1000237related to CVE-2021-26539
- CVE-2024-2150124 Feb 2024 related to CVE-2022-25887related to CVE-2016-1000237and 1 more
Exploited in the wild (CISA KEV) Not in KEV Priority score (0 to 100) High confidence Medium Low Link confidenceHow strong the evidence is that two CVEs are related. High: stated in the CVE text or linked in an advisory, or the same code was patched one release apart. Medium: the same code, or a version step plus a similar description. Low: similar description only.
CVEs in this family
Table view of the tree| CVE | Published | Title | Linked from | Priority |
|---|---|---|---|---|
| CVE-2016-1000237 | 23 Jan 2020 | sanitize-html before 1.4.3 has XSS · fixed in 1.4.3 | First in chain | 11.6 |
| CVE-2021-26539 | 8 Feb 2021 | Apostrophe Technologies sanitize-html before 2.3.1 does not properly handle internationalized domain name (IDN) which… · fixed in 2.3.1 | CVE-2016-1000237 · related · Medium | 16.0 |
| CVE-2022-25887 | 30 Aug 2022 | Regular Expression Denial of Service (ReDoS) · fixed in 2.7.1 | CVE-2016-1000237 · related · Medium | 18.7 |
| CVE-2024-21501 | 24 Feb 2024 | Versions of the package sanitize-html before 2.12.1 are vulnerable to Information Exposure when used on the backend… · fixed in 2.12.1 | CVE-2022-25887 · related · High | 16.4 |