Skip to main content
HighCodeOWASP A03:2021CWE-79

How to fix: insertAdjacentElement XSS sink

insertAdjacentElement splices a live DOM node into the document. When the node is built from attacker-controlled input, it bypasses HTML-string sanitizers because no HTML parsing is performed.

Why it matters

Attacker-controlled DOM nodes can execute JavaScript in the page origin without HTML-parser sanitizers firing.

The `code-xss-insertadjacentelement` check verifies that the server does not expose the `xss-insertadjacentelement` 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. 1Treat any element passed to insertAdjacentElement as untrusted; build it server-side with escaping.
  2. 2Prefer insertAdjacentText for plain-text interpolation.
  3. 3If nodes must be created from strings, sanitize with DOMPurify before parsing into a node.

Code examples

Validate element type before insertAdjacentElement

JavaScript
// BAD: inserting user-controlled elements
element.insertAdjacentElement("afterend", userElement);

// GOOD: create elements programmatically from safe data
const el = document.createElement("span");
el.textContent = userText; // not innerHTML
element.insertAdjacentElement("afterend", el);

References

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

See every code check

Questions

How severe is insertAdjacentElement 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-insertadjacentelement, which stays the same between runs so you can filter, diff, or gate CI on it.
Which standards does insertAdjacentElement 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 insertadjacentelement 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

How to fix: insertAdjacentElement XSS sink | VulnRadar