How to fix: Password in GET Request URL
Password parameter found in URL.
Why it matters
Credentials exposed in browser history, server logs, referrer.
GET parameters appear in URL and are logged everywhere.
How to fix it
- 1Use POST for all forms with passwords.
Code examples
Use POST for password submission, never GET
<!-- BAD: password in GET request URL appears in server logs and history -->
<!-- <form method="GET" action="/login"> -->
<!-- GOOD: always POST credentials -->
<form method="POST" action="/api/login">
<input type="email" name="email" autocomplete="email" />
<input type="password" name="password" autocomplete="current-password" />
<button type="submit">Log in</button>
</form>References
Detected automatically by VulnRadar. The check id is password-in-get, 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 Password in GET Request 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 password-in-get, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Password in GET Request 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.