CWE-525 Information Exposure Through the Browser
What this means
SiteShadow flagged sensitive data being exposed in browser-accessible places (URLs, DOM, caches, client-side storage, referrers) where it can leak to other origins, extensions, shared devices, or support tooling.
Why it matters
Browser-exposed data can leak through history, caches, or UI.
- Token leakage via URLs/referrers (see
CWE-598). - Shared-device exposure if sensitive data is cached or persisted.
- XSS amplification: if sensitive data is in the DOM/storage, XSS can exfiltrate it.
Safer examples
1) Don't put secrets in the browser
Avoid placing tokens/passwords in query strings, DOM attributes, or JS-accessible storage.
2) Use secure cookies and server-side sessions
Prefer HttpOnly cookies and server-side session state where feasible (see S02 / CWE-614).
3) Use cache controls for sensitive pages
Disable caching where appropriate (varies by app and content sensitivity).
How SiteShadow detects it (high level)
- Flags sensitive values in URL construction, client-side storage, and HTML/DOM sinks.
- Uses heuristics for token/credential/PII-like keys in browser contexts.
References
- CWE-525: https://cwe.mitre.org/data/definitions/525.html
---