MediumContent
How to fix: Hidden Password Input Field
Password field with type=hidden.
Why it matters
May expose password in page source.
Hidden inputs are visible in HTML source.
How to fix it
- 1Never store passwords in hidden fields.
Code examples
Avoid storing passwords in hidden form fields
<!-- BAD: password in a hidden field is visible in source and form data -->
<!-- <input type="hidden" name="password" value="{{ password }}"> -->
<!-- GOOD: request the password again for re-authentication flows -->
<input type="password" name="password" autocomplete="current-password" />
<!-- Never pass passwords through hidden fields across multiple form steps -->References
Detected automatically by VulnRadar. The check id is hidden-password-field, 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 Hidden Password Input Field?
- 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 hidden-password-field, which stays the same between runs so you can filter, diff, or gate CI on it.
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.