InfoContent
How to fix: Form Disables Autocomplete
Form has autocomplete=off.
Why it matters
Prevents password manager functionality.
Users may enter weaker manual passwords.
How to fix it
- 1Allow autocomplete unless there's a specific reason.
Code examples
Remove autocomplete="off" from forms
<!-- autocomplete="off" prevents password manager autofill
and is ignored by most modern browsers for passwords -->
<!-- BAD -->
<!-- <form autocomplete="off"> -->
<!-- GOOD: allow autocomplete at form level,
set specific autocomplete values on each field -->
<form>
<input type="email" name="email" autocomplete="email" />
<input type="password" name="password" autocomplete="current-password" />
</form>References
Detected automatically by VulnRadar. The check id is form-autocomplete-off, 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 Form Disables Autocomplete?
- VulnRadar rates this info 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 form-autocomplete-off, 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.