Skip to main content

How to fix: Missing Autocomplete Attributes on Sensitive Fields

Sensitive input fields without proper autocomplete attributes.

Why it matters

Browsers may cache sensitive form data on shared or compromised devices.

The autocomplete attribute tells browsers how to handle form autofill.

How to fix it

  1. 1Add autocomplete="new-password" for registration fields.
  2. 2Add autocomplete="current-password" for login fields.
  3. 3Add appropriate autocomplete values for payment fields.

Code examples

Proper autocomplete

HTML
<input type="password" autocomplete="current-password" />
<input type="password" autocomplete="new-password" />

References

Detected automatically by VulnRadar. The check id is autocomplete-sensitive, stable across every scan so you can filter or diff on it.

See every content check

Questions

How severe is Missing Autocomplete Attributes on Sensitive Fields?
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 autocomplete-sensitive, 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.

Propose a checkHow a check is built

Scan your own site for missing autocomplete attributes on sensitive fields

VulnRadar runs this check and hundreds more against a URL in seconds. No agent to install, just paste a URL.

Or scan this site as a demoRead the docs

Missing Autocomplete Attributes on Sensitive Fields | VulnRadar