HighContent
How to fix: Password Field Type is Text
Password stored in text input instead of password type.
Why it matters
Password visible on screen.
Password fields should mask input.
How to fix it
- 1Use type='password' for password inputs.
Code examples
Default password fields to type="password" (hidden)
<!-- Password fields must default to hidden (type="password") -->
<div class="password-wrapper">
<input type="password" id="password" name="password" autocomplete="current-password" />
<button type="button" aria-label="Show password" onclick="togglePasswordVisibility()">
<!-- eye icon -->
</button>
</div>
<script>
function togglePasswordVisibility() {
const input = document.getElementById("password");
input.type = input.type === "password" ? "text" : "password";
}
</script>References
Detected automatically by VulnRadar. The check id is password-visible-default, 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 Field Type is Text?
- 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 password-visible-default, 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.