How to fix: Script with data: URI
Script tag using data: URI source.
Why it matters
Inline script execution via data URI.
data: URIs can embed script content.
How to fix it
- 1Block data: in CSP script-src.
Code examples
Block data: URI script execution via CSP
// Add to Content-Security-Policy:
// script-src 'self' -- blocks data: URIs for scripts by default
// Explicitly: script-src 'self'; object-src 'none';
// Never allow data: in script-src or object-src
// CSP example:
res.setHeader("Content-Security-Policy",
"default-src 'self'; script-src 'self'; object-src 'none'; data: in img-src only";
);References
Detected automatically by VulnRadar. The check id is data-uri-script, 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 Script with data: URI?
- 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 data-uri-script, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Script with data: URI 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.