How to fix: document.write() Outside Page Scripts
document.write()/document.writeln() found in the response body outside a <script> block, typically in an inline event-handler attribute. Calls inside <script> blocks are reported separately by the client-side scan.
Why it matters
document.write() can be hijacked to inject malicious content if any input is attacker-controlled.
document.write() is deprecated, blocks HTML parsing, and is a common XSS vector.
How to fix it
- 1Replace document.write() with DOM APIs (createElement, appendChild).
- 2Use innerHTML with DOMPurify if HTML insertion is needed.
Code examples
Safe alternative
// BAD: document.write('<p>' + text + '</p>');
// GOOD:
const p = document.createElement('p');
p.textContent = text;
document.body.appendChild(p);References
Detected automatically by VulnRadar. The check id is document-write-usage, 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 document.write() Outside Page Scripts?
- VulnRadar rates this low 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 document-write-usage, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does document.write() Outside Page Scripts 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.