Password Field Autocomplete Enabled

A password field does not disable browser autocompletion, so browsers may offer to save the credentials, although current browsers ignore that setting for login fields.

SeverityInformational
CVSS 3.10 CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:N Open in the calculator
CVSS 4.00 CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:P/VC:N/VI:N/VA:N/SC:N/SI:N/SA:N Open in the calculator
CWECWE-522: Insufficiently Protected Credentials
OWASP Top 10A06:2025 Insecure Design
CategorySecurity Misconfiguration

Description

The application's login or password forms do not set autocomplete="off" on the password field or on the form, so browsers may offer to save the credentials entered and fill them in later. Scanners commonly report this as a password field with autocomplete enabled.

Current browsers do not honour autocomplete="off" on login fields: their built-in password managers offer to save credentials whatever the attribute says, because saved, unique passwords are considered better for users than reused, memorable ones. The attribute still stops browsers saving entries for other form fields, and browsers use autocomplete="new-password" to avoid filling in a saved password where a new one is being set. In current browsers the finding therefore has no direct impact and is largely informational.

Where a browser does save a password, anyone who can use the same computer and browser profile can log in as that user or recover the password from the browser's store, and malware running as the user can extract saved passwords. The finding remains relevant, and the concern greatest, for applications used on shared, public or kiosk computers, where a password saved on one user's behalf is available to the next person using the same browser profile.

Remediation

Do not rely on autocomplete="off" to protect credentials: current browsers ignore it for login fields, and blocking password managers tends to push users towards weaker, reused passwords. Instead:

  • Use accurate autocomplete values so that password managers behave predictably: username and current-password on login forms, and new-password where a password is set or changed.
  • Protect accounts with multi-factor authentication, so that a password recovered from a browser is not enough to log in.
  • Where the application is used on shared or kiosk computers, manage those browsers centrally to turn off password saving, for example with the PasswordManagerEnabled policy in Chrome and Edge, and clear profiles between users.
  • Advise users not to save passwords on shared computers, and apply short session timeouts there.

Confirm any change by reviewing the form markup and, on managed computers, checking that the browser no longer offers to save the password.

References


Add This Finding to Your Library

In Pental this write-up is in Settings, Library. Add to my library copies it into your own, rated in your firm's CVSS version, ready to put in your own words.

Free trial  ·  No card required

Only need the reporting? Our reporting tool is free and open source, with the same library.


More Web Applications Findings

Every Web Applications finding