DOMSanitizer is a DOM/SVG/MathML Sanitizer for PHP 7.3+

Why it is Yellow

• CVSS 4.7 medium
• On your watchlist: php

References

• https://github.com/rhukster/dom-sanitizer/commit/10f97807e4501d60f63987f2e76a38cdbf312dcb
• https://github.com/rhukster/dom-sanitizer/commit/fb8f758b41134fc5fb2f563666f2330c69e31f94
• https://github.com/rhukster/dom-sanitizer/releases/tag/1.0.15
• https://github.com/rhukster/dom-sanitizer/security/advisories/GHSA-wcj2-r6vg-rm97
• https://github.com/rhukster/dom-sanitizer/security/advisories/GHSA-wcj2-r6vg-rm97

Original description

DOMSanitizer is a DOM/SVG/MathML Sanitizer for PHP 7.3+. Prior to version 1.0.15, the isDangerousUrl() method is responsible for rejecting dangerous URL values in the href and xlink:href attributes. The weakness is that "javascript:" is rejected as a scheme, while "data:" is rejected only when the literal substring onload appears in the URL value (/^data:.*onload/i). Because data: payloads are routinely Base64-encoded, the dangerous content (<script>, event handlers, etc.) is invisible to that substring test. A URL such as data:text/html;base64,… therefore survives in href / xlink:href, even though the decoded payload is active markup. This is an incomplete input-validation / sanitization defect in the sanitizer itself. This issue has been patched in version 1.0.15.