How to fix: JWT Token in Page Source
JSON Web Token found in HTML source.
Why it matters
Exposed tokens allow session hijacking.
JWTs in page source can be stolen by XSS attacks.
How to fix it
- 1Never embed JWTs in HTML; use HttpOnly cookies.
Code examples
Remove JWTs from HTML: use HttpOnly cookies
// JWTs embedded in HTML are visible in source view and accessible to XSS
// BAD: <script>window.__TOKEN__ = "eyJ..."</script>
// GOOD: server sets HttpOnly cookie on authentication
res.setHeader("Set-Cookie",
`session=${jwt}; HttpOnly; Secure; SameSite=Strict; Path=/`
);
// Token is invisible to JavaScript; sent automatically with all requestsReferences
Detected automatically by VulnRadar. The check id is jwt-in-html, 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 in Page 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 jwt-in-html, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does JWT Token in Page Source 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.