How to fix: Angular interpolation bypass
AngularJS (1.x) template injection: user-controlled values rendered via {{ }} or ng-bind-html-unsafe are XSS sinks.
Why it matters
Migrate off AngularJS 1.x; never bind user data into ng-bind-html-unsafe
AngularJS (1.x) template injection: user-controlled values rendered via {{ }} or ng-bind-html-unsafe are XSS sinks.
How to fix it
- 1Migrate off AngularJS 1.x; never bind user data into ng-bind-html-unsafe
Code examples
Use Angular interpolation safely: avoid innerHTML binding
// Angular auto-escapes interpolation: {{ userInput }} is safe
// BAD: bypasses Angular's sanitization
// <div [innerHTML]="userHtml"></div> // only safe if sanitized
// GOOD: use {{ }} for text content (auto-escaped)
// <p>{{ userName }}</p> // safe, Angular escapes this
// For HTML: use DomSanitizer.sanitize() before bindingReferences
Detected automatically by VulnRadar. The check id is code-angular-interpolation-bypass, stable across every scan so you can filter or diff on it.
More code checks
- CriticalForm Submits Data Over Insecure HTTP
- MediumPotential Prototype Pollution Sinks Detected
- HighPotential Command Injection Vectors
- HighJWT Decoded Without Signature Verification
- HighPotential Path Traversal Vulnerability
- HighInsecure Authentication Mechanisms Detected
- HighPotential Insecure Deserialization
- Mediumeval() Usage in Inline Scripts
Questions
- How severe is Angular interpolation bypass?
- VulnRadar rates this medium severity in the code 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 code-angular-interpolation-bypass, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Angular interpolation bypass 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.