How to fix: jQuery global event handler
$(document).on('click', sel, fn) can be triggered by an attacker-controlled selector.
Why it matters
Bind handlers to specific elements, not document
$(document).on('click', sel, fn) can be triggered by an attacker-controlled selector.
How to fix it
- 1Bind handlers to specific elements, not document
Code examples
Scope event handlers to specific elements
// BAD: global event listeners can be triggered by any element
$(document).on("click", userDefinedSelector, handler);
// GOOD: scope to a specific container you control
$("#app-container").on("click", ".btn-action", handler);
// Never let user input define the selector stringReferences
Detected automatically by VulnRadar. The check id is code-jquery-global-event, 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 global event handler?
- VulnRadar rates this low 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-global-event, which stays the same between runs so you can filter, diff, or gate CI on it.
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.