MediumContent
How to fix: Password Field with Short maxlength
Password input with very short maxlength.
Why it matters
Artificially limits password strength.
Short passwords are easier to crack.
How to fix it
- 1Allow at least 64-128 character passwords.
Code examples
Set appropriate maxlength values on inputs
<!-- NIST recommends allowing passwords up to 64+ characters -->
<input type="password" name="password" maxlength="128" autocomplete="current-password" />
<input type="email" name="email" maxlength="254" autocomplete="email" />
<!-- Set generous limits that do not frustrate users or break password managers -->
<!-- Validate length server-side as well -->References
Detected automatically by VulnRadar. The check id is input-maxlength-short, 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 with Short maxlength?
- 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 input-maxlength-short, 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.