How to fix: Sensitive Data in localStorage
Sensitive data patterns being stored in localStorage.
Why it matters
Data accessible to any script on the page.
localStorage is not encrypted and accessible via XSS.
How to fix it
- 1Use secure, HttpOnly cookies for sensitive data.
Code examples
Store tokens in HttpOnly cookies, not localStorage
// BAD: tokens in localStorage are readable by any JS (XSS)
// localStorage.setItem("auth_token", token);
// GOOD: server sets an HttpOnly cookie
res.setHeader("Set-Cookie",
`session=${token}; HttpOnly; Secure; SameSite=Strict; Path=/; Max-Age=3600`
);
// HttpOnly cookies cannot be read by JavaScript at allReferences
Detected automatically by VulnRadar. The check id is localstorage-sensitive, 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 Sensitive Data in localStorage?
- 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 localstorage-sensitive, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Sensitive Data in localStorage map to?
- It maps to CWE-312. In the OWASP Top 10 it falls under A02: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.