Know every vulnerabilitybefore it knows you.
DevGuard continuously monitors your dependencies and alerts you when CVEs like this one affect your stack — with real-time threat intelligence built for developers.
GHSA-qvpj-w7xj-r6w9
No affected components available
Users registering via the user:register_form tag will have their password confirmation stored in plain text in their user file.
Impact
This only affects sites matching all of the following conditions:
- Running Statamic versions between 5.3.0 and 5.6.1. (This version range represents only one calendar week)
- Using the
user:register_formtag. - Using file-based user accounts. (Does not affect users stored in a database.)
- Has users that have registered during that time period. (Existing users are not affected.)
The password is only visible to users that have access to read user yaml files, typically developers of the application itself.
Patches
The issue has been patched in 5.6.2, however any users registered during that time period and using the affected version range will still have the the password_confirmation value in their yaml files.
We recommend that affected users have their password reset. The following query can be entered into php artisan tinker and will output a list of affected emails:
Statamic\Facades\User::query()->whereNotNull('password_confirmation')->get()->map->email
The following can be entered into tinker and will clear both password_confirmation as well as their existing password. They will be required to reset their password before their next login attempt.
Statamic\Facades\User::query()
->whereNotNull('password_confirmation')->get()
->each(fn ($user) => $user->remove('password_confirmation')->passwordHash(null)->save());
References
If you are committing user files to a public git repo, you may consider clearing the sensitive data from the git history. You can use the following links for details.
- https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository
- https://dev.to/balogh08/cleaning-your-git-history-safely-removing-sensitive-data-10i5
The vulnerability requires local access to the device to be exploited. It is difficult for an attacker to exploit this vulnerability and may require special conditions. An attacker needs high-level or administrative privileges. The attacker needs the user to perform some action, like clicking a link. The impact is confined to the system where the vulnerability exists. There is a low impact on the confidentiality of the information.
Limited exploitation activity has been observed. Close monitoring and planned remediation are recommended.
The exploit probability is very low. The vulnerability is unlikely to be exploited in the next 30 days.
We did not find any exploit available. Neither in GitHub repositories nor in the Exploit-Database.
Browse More
Continuously monitor your dependencies and get alerted when vulnerabilities like this one affect your stack.
Checkout DevGuard