How to fix: Password Fields Missing Name Attribute
Password input fields are missing a name attribute, hindering form submission and password manager functionality.
Why it matters
Password managers may not correctly identify or fill these fields, discouraging their use.
Password managers rely on the input's name (and autocomplete) attributes to correctly identify and autofill fields. Missing autocomplete alone is covered separately by the autocomplete-sensitive check.
How to fix it
- 1Add a name attribute to all password fields.
- 2Use autocomplete='current-password' for login and 'new-password' for registration.
Code examples
Proper password field
<input type="password" name="password" autocomplete="current-password" />References
Detected automatically by VulnRadar. The check id is password-input-no-name, 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 Fields Missing Name Attribute?
- VulnRadar rates this low 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-input-no-name, 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.