Craft CMS: Arbitrary user password reset leading to administrator account takeover
Published 6 Aug 2026 · Updated 3 Sept 2026
Affected package
- Affected
- >=5.0.0-RC1 <5.10.8
- Fixed in
- 5.10.8
composer require craftcms/cms:^5.10.8Details
The vulnerability allows any authenticated user to change their own password without providing the current password or having an active elevated session. It also allows the attacker to change other users’ passwords if the attacker’s account has edit users permission (which doesn’t allow changing others’ passwords) and lacks Administrate users permission (which is required to change others’ passwords).
The vulnerability exists in the elements/save action when saving a User element. The UserPasswordValidator applies only a safe validator to the newPassword field without an on scenario restriction. This makes newPassword mass-assignable during the generic element save flow, completely bypassing the dedicated users/set-password action that enforces elevated session verification.
An attacker with any authenticated session (whether it’s hijacked or a normal / low-privileged user) can change their own password, and potentially take over administrator accounts.
Required Permissions
- Access the control panel
- Edit users (needed for the account takeover attack scenario)
Impact
- Any authenticated user can change their own password without providing their current password.
- Users with Edit users permission can change any user’s password, including administrators.
Is GHSA-p8x7-9vfw-p7vc in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected craftcms/cms, and gives you the command that fixes it.
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.