{"schemaVersion":1,"url":"https://cve.openhack.com/cve/CVE-2026-100370","id":"CVE-2026-100370","title":"DOMSanitizer - Incomplete data: URL Sanitization in DOMSanitizer::isDangerousUrl() Allows Base64-Encoded Payloads to Bypass href and xlink:href Validation","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 rou","descriptionLong":"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.","published":"2026-09-28T20:07:09.470Z","updated":"2026-10-28T02:30:38.207741289Z","reserved":"2026-09-25T19:19:54.699Z","status":"Deferred","rejected":false,"assigner":"GitHub_M","metric":{"version":"3.1","score":4.7,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:N/A:N","rating":"medium","source":"GitHub_M"},"metrics":[{"version":"3.1","score":4.7,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:N/A:N","rating":"medium","source":"GitHub_M"},{"version":"3.1","score":4.7,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:N/A:N","rating":"medium","source":"github.com"},{"version":"3.1","score":4.7,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:N/A:N","rating":"medium","source":"OSV"}],"rating":"medium","products":["rhukster dom-sanitizer"],"affectedProducts":[{"vendor":"rhukster","product":"dom-sanitizer","defaultStatus":null,"versions":[{"version":"< 1.0.15","status":"affected"}],"platforms":[]}],"packages":[],"cwes":["CWE-20"],"aliases":["GHSA-wcj2-r6vg-rm97"],"references":[{"url":"https://github.com/rhukster/dom-sanitizer/security/advisories/GHSA-wcj2-r6vg-rm97","tags":["x_refsource_CONFIRM","exploit","advisory"]},{"url":"https://github.com/rhukster/dom-sanitizer/commit/10f97807e4501d60f63987f2e76a38cdbf312dcb","tags":["x_refsource_MISC","fix"]},{"url":"https://github.com/rhukster/dom-sanitizer/commit/fb8f758b41134fc5fb2f563666f2330c69e31f94","tags":["x_refsource_MISC","fix"]},{"url":"https://github.com/rhukster/dom-sanitizer/releases/tag/1.0.15","tags":["x_refsource_MISC","web"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/100xxx/CVE-2026-100370.json","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-100370","tags":["advisory"]}],"patchReferenced":true,"fixAvailable":true,"exploitReferenced":true,"kev":false,"kevAdded":null,"kevDue":null,"kevEntry":null,"ssvc":{"exploitation":"poc","automatable":"no","technicalImpact":"partial"},"epss":0.00274,"epssPercentile":0.20109,"sources":[{"name":"CVE List","url":"https://www.cve.org/CVERecord?id=CVE-2026-100370","ok":true},{"name":"NVD","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-100370","ok":true,"note":"Deferred"},{"name":"OSV","url":"https://osv.dev/vulnerability/CVE-2026-100370","ok":true,"note":"0 packages"},{"name":"CISA KEV","url":"https://www.cisa.gov/known-exploited-vulnerabilities-catalog","ok":true,"note":"not listed"},{"name":"EPSS","url":"https://api.first.org/data/v1/epss?cve=CVE-2026-100370","ok":true,"note":"scored 2026-11-19"}],"aiTitle":false,"tech":[],"critical":[],"attention":null}