Improper Input Validation in sanitize-html - sanitize-html

Description

Apostrophe Technologies sanitize-html before 2.3.2 does not properly validate the hostnames set by the “allowedIframeHostnames” option when the “allowIframeRelativeUrls” is set to true, which allows attackers to bypass hostname whitelist for iframe element, related using an src value that starts with “/\example.com”.

Recommendation

Update the sanitize-html package to the latest compatible version. Followings are version details:

• Affected version(s): < 2.3.2
• Patched version(s): 2.3.2

References

• GHSA-mjxr-4v3x-q3m4
• advisory.checkmarx.net
• CVE-2021-26540
• CWE-20
• CAPEC-310
• OWASP 2021-A3
• OWASP 2021-A6

Related Issues

• Improper Input Validation in sanitize-html - CVE-2021-26539
• sanitize-html has incomplete URI scheme validation in that allows javascript: URIs through action, formaction, data, pos - CVE-2026-53606
• Improper Input Validation in is-email - CVE-2021-36716
• sanitize-html Information Exposure vulnerability - CVE-2024-21501

You might also like:

How to Secure your NodeJs Express Javascript Application - part 1

How to Secure your NodeJs Express Javascript Application - part 2

10 Secure Coding Best Practices to Follow in Every Project

Tags:

npm

sanitize-html