How to fix: Username field missing autocomplete="username"
A username or login field does not specify autocomplete="username", hindering password manager autofill.
Why it matters
Without autocomplete="username", password managers cannot reliably identify the username field, reducing autofill accuracy and discouraging password manager use.
Set autocomplete="username" on username and login identifier fields.
How to fix it
- 1Add autocomplete="username" to the username/login field
- 2Pair with autocomplete="current-password" on the password field
Code examples
Login form with autocomplete
<input type="email" name="email" autocomplete="username" />
<input type="password" name="password" autocomplete="current-password" />References
Detected automatically by VulnRadar. The check id is autocomplete-username, stable across every scan so you can filter or diff on it.
More headers checks
Questions
- How severe is Username field missing autocomplete="username"?
- VulnRadar rates this info severity in the headers 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 autocomplete-username, 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.