How to fix: Potential DOM Clobbering
HTML elements with IDs that could clobber globals.
Why it matters
JavaScript globals can be overwritten.
HTML id/name attributes create global variables.
How to fix it
- 1Avoid relying on global variable names from DOM.
Code examples
Use getElementById instead of relying on named globals
// BAD: window.myForm or document.myForm can be clobbered by attacker HTML
// <form name="myForm"> clobbers window.myForm
// GOOD: use explicit DOM methods
const form = document.getElementById("my-form");
if (!(form instanceof HTMLFormElement)) throw new Error("Form not found");
// Also: set Content-Security-Policy to block attacker HTML injectionReferences
Detected automatically by VulnRadar. The check id is dom-clobbering-vulnerable, 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 Potential DOM Clobbering?
- VulnRadar rates this medium 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 dom-clobbering-vulnerable, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Potential DOM Clobbering 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.