How to fix: jQuery .html() with user input
$el.html(userInput) executes arbitrary HTML. Always escape or use .text().
Why it matters
Use .text() or escape user input via a DOMPurify-like library
$el.html(userInput) executes arbitrary HTML. Always escape or use .text().
How to fix it
- 1Use .text() or escape user input via a DOMPurify-like library
Code examples
Avoid .html() with user content in jQuery
// BAD: .html() with user input executes scripts
$("#content").html(userInput);
// GOOD: .text() for plain text
$("#content").text(userInput);
// If HTML is needed, sanitize first
import DOMPurify from "dompurify";
$("#content").html(DOMPurify.sanitize(userInput));References
Detected automatically by VulnRadar. The check id is code-jquery-html, stable across every scan so you can filter or diff on it.
More code checks
- CriticalForm Submits Data Over Insecure HTTP
- MediumPotential Prototype Pollution Sinks Detected
- HighPotential Command Injection Vectors
- HighJWT Decoded Without Signature Verification
- HighPotential Path Traversal Vulnerability
- HighInsecure Authentication Mechanisms Detected
- HighPotential Insecure Deserialization
- Mediumeval() Usage in Inline Scripts
Questions
- How severe is jQuery .html() with user input?
- 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-jquery-html, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does jQuery .html() with user input 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.