How to fix: JWT Token Exposed in URL
A JSON Web Token was found embedded in a URL within the page HTML.
Why it matters
The token appears in browser history, proxy logs, server logs, and Referer headers.
JWTs in URLs persist in numerous locations, creating many avenues for token theft.
How to fix it
- 1Transmit tokens in HTTP headers (Authorization: Bearer) instead of URLs.
- 2Use HTTP-only secure cookies.
- 3Implement short-lived single-use tokens.
Code examples
Fetch with header
// BAD: Token in URL
fetch('/api/data?token=eyJ...');
// GOOD: Token in header
fetch('/api/data', { headers: { 'Authorization': 'Bearer ' + token } });References
Detected automatically by VulnRadar. The check id is jwt-in-url, 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 JWT Token Exposed in URL?
- VulnRadar rates this critical 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 jwt-in-url, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does JWT Token Exposed in URL map to?
- It maps to CWE-598. 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.