Skip to main content
HighCodeOWASP A03:2021CWE-79

How to fix: Range.createContextualFragment XSS sink

Range.createContextualFragment(fragString) parses HTML and returns a DocumentFragment. Passing user-controlled HTML directly into the fragment lets attackers inject <script> or event-handler nodes that execute immediately on insertion.

Why it matters

Attacker-controlled HTML strings execute JavaScript in the page origin the moment the fragment is inserted.

The `code-xss-createcontextualfragment` check verifies that the server does not expose the `xss-createcontextualfragment` weakness in the code category. The detection runs against the response headers, body, or auxiliary probes (DNS, TLS, async fetch) as appropriate.

How to fix it

  1. 1Sanitize the HTML string with DOMPurify before passing it to createContextualFragment.
  2. 2Prefer DOMParser.parseFromString with explicit text/html and sanitization.
  3. 3Use textContent for text-only insertion.

Code examples

Sanitize before createContextualFragment

JavaScript
// BAD: executes scripts in the fragment
const range = document.createRange();
const fragment = range.createContextualFragment(userHtml);

// GOOD: sanitize first
import DOMPurify from "dompurify";
const clean = DOMPurify.sanitize(userHtml);
const fragment = range.createContextualFragment(clean);

References

Detected automatically by VulnRadar. The check id is code-xss-createcontextualfragment, stable across every scan so you can filter or diff on it.

See every code check

Questions

How severe is Range.createContextualFragment XSS sink?
VulnRadar rates this high severity in the code category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
Does VulnRadar check for this automatically?
Yes. It runs as part of every scan under the check id code-xss-createcontextualfragment, which stays the same between runs so you can filter, diff, or gate CI on it.
Which standards does Range.createContextualFragment XSS sink map to?
It maps to CWE-79. In the OWASP Top 10 it falls under A03:2021.

Missing a check?

The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.

Propose a checkHow a check is built

Scan your own site for range.createcontextualfragment xss sink

VulnRadar runs this check and hundreds more against a URL in seconds. No agent to install, just paste a URL.

Or scan this site as a demoRead the docs

Range.createContextualFragment XSS sink fix | VulnRadar