LowContent
How to fix: CDN Scripts Without Fallback
CDN-hosted scripts without local fallback.
Why it matters
Site breaks if CDN is unavailable or compromised.
SRI helps but local fallback ensures availability.
How to fix it
- 1Add onerror fallback to local copy for critical scripts.
Code examples
Add SRI and a local fallback for CDN resources
<script
src="https://cdn.example.com/jquery.min.js"
integrity="sha384-HASH"
crossorigin="anonymous"
></script>
<script>
// Fallback if CDN fails
if (typeof jQuery === "undefined") {
document.write('<script src="/libs/jquery.min.js"><\/script>');
}
</script>References
Detected automatically by VulnRadar. The check id is cdn-fallback-missing, 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 CDN Scripts Without Fallback?
- 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 cdn-fallback-missing, 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.