How to fix: Sensitive data in Web Storage API
The page stores potentially sensitive data in localStorage or sessionStorage, which is accessible to all same-origin JavaScript.
Why it matters
Data in localStorage and sessionStorage is accessible to any JavaScript running on the same origin, an XSS attack can exfiltrate all stored tokens, user data, and application state without the user's knowledge.
Web Storage should not contain authentication tokens, session identifiers, or PII. Use HttpOnly cookies for sensitive session state.
How to fix it
- 1Move session tokens to HttpOnly cookies
- 2Encrypt sensitive data before storing if Web Storage is unavoidable
- 3Limit Web Storage to non-sensitive preferences only
Code examples
Avoid storing sensitive data in localStorage
// Unsafe: tokens in localStorage are accessible to XSS
localStorage.setItem('auth_token', token);
// Better: use httpOnly cookies set by the server
// res.cookie('session', token, { httpOnly: true, secure: true, sameSite: 'strict' })
// If localStorage is required, never store secrets,
// use a short-lived session ID that maps to server stateReferences
Detected automatically by VulnRadar. The check id is storage-api-usage, stable across every scan so you can filter or diff on it.
More content checks
- MediumPotential Open Redirect Parameters
- HighDirectory Listing Appears Enabled
- MediumSensitive File References Detected
- HighPotentially Outdated JavaScript Libraries
- Inforobots.txt Present - Review Manually
- InfoCMS / Technology Fingerprinting
- MediumPotentially Dangerous Inline JavaScript
- LowServer version disclosed in response header
Questions
- How severe is Sensitive data in Web Storage API?
- VulnRadar rates this medium severity in the content 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 storage-api-usage, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Sensitive data in Web Storage API 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.