How to fix: localStorage storing PII
localStorage is not encrypted and is readable by any JS that runs in the same origin.
Why it matters
Don't store PII, tokens, or session identifiers in localStorage
localStorage is not encrypted and is readable by any JS that runs in the same origin.
How to fix it
- 1Don't store PII, tokens, or session identifiers in localStorage
Code examples
Avoid storing PII in localStorage
// BAD: PII readable by any same-origin script (XSS risk)
// localStorage.setItem("user_email", email);
// GOOD: store only non-sensitive identifiers client-side
localStorage.setItem("theme", "dark"); // preferences: OK
localStorage.setItem("userId", hashedId); // non-sensitive ID: OK
// PII (email, name, SSN) should stay server-side
// Use session cookie to identify the user server-sideReferences
Detected automatically by VulnRadar. The check id is code-local-storage-pii, 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 localStorage storing PII?
- 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-local-storage-pii, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does localStorage storing PII 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.