How to fix: Remember-Me Token in URL
Remember-me token exposed in URL.
Why it matters
Persistent auth token leaked in referrer and logs.
Remember-me tokens should be in cookies, not URLs.
How to fix it
- 1Store remember-me tokens in secure, HttpOnly cookies.
Code examples
Secure remember-me tokens in HttpOnly cookies
// Remember-me tokens must be:
// 1. Cryptographically random (not predictable)
// 2. Stored in HttpOnly+Secure cookie (not localStorage)
// 3. Single-use or rotated on each use
import { randomBytes } from "crypto";
const rememberToken = randomBytes(32).toString("hex");
// Store hash of token in DB, not plaintext
await db.rememberTokens.create({ userId, tokenHash: sha256(rememberToken) });
res.setHeader("Set-Cookie",
`remember=${rememberToken}; HttpOnly; Secure; SameSite=Strict; Path=/; Max-Age=2592000`
);References
Detected automatically by VulnRadar. The check id is remember-me-token, 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 Remember-Me Token in URL?
- 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 remember-me-token, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Remember-Me Token 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.