How to fix: Paste disabled on password field
The password input field has JavaScript that prevents pasting, making password manager use difficult.
Why it matters
Blocking paste on password fields forces users to type passwords manually, discouraging the use of password managers and leading to shorter, weaker passwords that are easier to type. This increases the risk of account compromise.
NCSC and NIST recommend allowing paste on password fields to encourage password manager use.
How to fix it
- 1Remove any onpaste="return false;" or paste event listeners from password fields
- 2Allow paste on all password, email, and username fields
- 3Consider allowing browsers to autofill credentials via autocomplete="current-password"
Code examples
Remove paste prevention from password fields
// Remove any paste-blocking code:
// BAD: never block paste on password fields
// document.querySelector('[type=password]').addEventListener('paste', e => e.preventDefault());
// Password managers use paste. Blocking it forces weak, memorable passwords.
// Simply allow default browser behavior.References
Detected automatically by VulnRadar. The check id is password-no-paste, 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 Paste disabled on password field?
- 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-no-paste, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Paste disabled on password field map to?
- It maps to CWE-521. In the OWASP Top 10 it falls under A07:2021.
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.