Skip to main content
MediumCodeOWASP A02:2021CWE-312

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

  1. 1Store tokens in HttpOnly cookies.

Code examples

Prefer HttpOnly cookies over sessionStorage for tokens

TypeScript
// 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.

See every code check

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.

Propose a checkHow a check is built

Scan your own site for tokens in sessionstorage

VulnRadar runs this check and hundreds more against a URL in seconds. No agent to install, just paste a URL.

Or scan this site as a demoRead the docs

How to fix: Tokens in sessionStorage | VulnRadar