Skip to main content
HighContentOWASP A02:2021CWE-522

How to fix: Bearer Token Exposed in Source

Bearer token found in page source.

Why it matters

Direct credential exposure.

Bearer tokens grant API access.

How to fix it

  1. 1Never embed tokens in HTML, use secure storage.

Code examples

Remove bearer tokens from HTML and client-visible locations

TypeScript
// Bearer tokens embedded in HTML or JS bundles are readable by any script
// BAD: window.__BEARER_TOKEN__ = "abc123" in HTML

// GOOD: fetch tokens from a secure API endpoint when needed
const res = await fetch("/api/token", { credentials: "include" });
const { token } = await res.json();
// Or better: use HttpOnly cookies so the token is never accessible to JS

References

Detected automatically by VulnRadar. The check id is bearer-token-exposed, stable across every scan so you can filter or diff on it.

See every content check

Questions

How severe is Bearer Token Exposed in Source?
VulnRadar rates this high 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 bearer-token-exposed, which stays the same between runs so you can filter, diff, or gate CI on it.
Which standards does Bearer Token Exposed in Source map to?
It maps to CWE-522. 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 bearer token exposed in source

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: Bearer Token Exposed in Source | VulnRadar