How to fix: Tokens in sessionStorage
Authentication tokens stored in sessionStorage.
Why it matters
Vulnerable to XSS-based token theft.
sessionStorage is accessible via JavaScript.
How to fix it
- 1Store tokens in HttpOnly cookies.
Code examples
Prefer HttpOnly cookies over sessionStorage for tokens
// BAD: sessionStorage is still accessible to XSS
// sessionStorage.setItem("token", jwt);
// GOOD: server-side session with HttpOnly cookie
res.setHeader("Set-Cookie",
`session=${sessionId}; HttpOnly; Secure; SameSite=Strict; Path=/`
);References
Detected automatically by VulnRadar. The check id is sessionstorage-tokens, 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 Tokens in sessionStorage?
- 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 sessionstorage-tokens, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Tokens in sessionStorage 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.