How to fix: Passwords stored in sessionStorage
sessionStorage.setItem('password', pwd) or sessionStorage.setItem('pwd', val) keeps plaintext credentials in the browser for the lifetime of the tab. Any XSS reads it instantly.
Why it matters
Plaintext password exfiltration via XSS yields direct credential reuse against other services.
The `code-auth-sessionstorage-passwords` check verifies that the server does not expose the `auth-sessionstorage-passwords` weakness in the code category. The detection runs against the response headers, body, or auxiliary probes (DNS, TLS, async fetch) as appropriate.
How to fix it
- 1Never persist plaintext passwords client-side; send them once to the server over HTTPS.
- 2Issue an opaque session token via Set-Cookie HttpOnly; Secure; SameSite=Strict.
- 3Adopt WebAuthn for passwordless flows where possible.
Code examples
Never store passwords in sessionStorage
// NEVER store passwords in sessionStorage: they survive page reloads
// and are accessible to any same-origin XSS
// sessionStorage.setItem("password", password);
// Submit the password directly to the server:
const res = await fetch("/api/login", {
method: "POST",
body: JSON.stringify({ email, password }),
headers: { "Content-Type": "application/json" },
});
// Server returns a session cookie: password never stored client-sideReferences
Detected automatically by VulnRadar. The check id is code-auth-sessionstorage-passwords, 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 Passwords stored in sessionStorage?
- VulnRadar rates this critical 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-auth-sessionstorage-passwords, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Passwords stored 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.