How to fix: Dangerous HTML Attributes Detected
Potentially dangerous HTML attributes like inline event handlers, javascript: URIs.
Why it matters
Inline event handlers and javascript: URIs are common XSS vectors.
Inline event handlers, javascript: protocol links, and data: URIs embedding HTML/JS are all classic XSS injection points.
How to fix it
- 1Remove all javascript: protocol links.
- 2Move inline event handlers to external JavaScript files.
- 3Implement CSP with 'unsafe-inline' disabled.
Code examples
Safe pattern
<!-- BAD -->
<a href="javascript:void(0)" onclick="doStuff()">Click</a>
<!-- GOOD -->
<button type="button" id="action-btn">Click</button>References
Detected automatically by VulnRadar. The check id is dangerous-html-attrs, stable across every scan so you can filter or diff on it.
More content checks
- MediumPotential Open Redirect Parameters
- HighDirectory Listing Appears Enabled
- MediumSensitive File References Detected
- HighPotentially Outdated JavaScript Libraries
- Inforobots.txt Present - Review Manually
- InfoCMS / Technology Fingerprinting
- MediumPotentially Dangerous Inline JavaScript
- LowServer version disclosed in response header
Questions
- How severe is Dangerous HTML Attributes Detected?
- VulnRadar rates this high severity in the content 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 dangerous-html-attrs, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Dangerous HTML Attributes Detected 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.