Sensitive Account Changes Without Re-Authentication
A signed-in session can change the password, email address or multi-factor settings without the current password, so anyone holding the session can take the account over for good.
| Severity | Medium |
| CVSS 3.1 | 6.8 CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N Open in the calculator |
| CVSS 4.0 | 7.6 CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N Open in the calculator |
| CWE | CWE-620: Unverified Password Change |
| OWASP Top 10 | A07:2025 Authentication Failures |
| MITRE ATT&CK | T1098 Account Manipulation, T1531 Account Access Removal |
| Category | Insecure Design |
Description
Some account changes amount to control of the account: changing the password, the email address or telephone number used for recovery, multi-factor authentication settings and recovery codes and, depending on the application, linked identities, API keys, or payout and payment details. The application allows these changes on the strength of the current session alone, without asking for the current password or a fresh multi-factor check.
A session is weaker evidence of identity than the password: it may have been stolen through cross-site scripting, a leaked token or malware, or simply used by someone else on an unattended or shared device. Without a re-authentication step, an attacker with temporary access to the session can turn it into permanent control: they can change the password and recovery details, or turn off multi-factor authentication, and so lock the legitimate user out and keep control of the account after the session ends, leaving recovery to depend on the organisation's support process. The attacker first needs the session, but this weakness decides whether that brief access becomes a lasting account takeover, and the impact is greatest for administrative and other high-value accounts. Where cross-site request forgery affects these functions, the same gap makes it more damaging.
The weakness is identified by making each sensitive change in an authenticated session and observing whether the current password or a second factor is requested, and whether the change can be made by replaying the request without that value. Checks that appear in the user interface but are not enforced by the server are common, so the request should also be replayed with the field removed. A change of email address that takes effect without confirmation is a closely related weakness.
Remediation
Require fresh proof of identity before any change that affects control of the account:
- Ask for the current password, or a multi-factor confirmation for users who have set it up, before changing the password, email address, telephone number, multi-factor settings or recovery codes, and before other sensitive actions such as creating API keys or changing payment details. Enforce the check on the server, as part of the same request as the change.
- Alternatively, require a recent authentication: record the time of the last full sign-in and ask the user to sign in again if it is older than a short limit. With federated sign-in, the OpenID Connect
max_ageandprompt=loginparameters and theauth_timeclaim support this. - For email address changes, confirm the new address with a link before the change takes effect, and notify the old address with a way to reverse it.
- Notify the user of every sensitive change through an existing channel, and end other sessions after a password change.
- Rate limit the current password check, as it could otherwise be used to guess the password.
Confirm the fix by repeating each sensitive change with the current password missing or wrong, and checking that the server refuses it.
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 trialYour trial starts when your portal goes live, not when you sign up, so the time you spend setting up does not count. · No card required
Only need the reporting? Our reporting tool is free and open source, with the same library.