CVE-2024-36119: Password confirmation stored in plain text via registration form in statamic/cms
Users registering via the user:registerform 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:registerform tag. - Using file-based user accounts.
Published Jun 2, 2024
Affected packages
statamic/cms
- Ecosystem
- Composer (PHP)
- Affected
- >= 5.3.0, < 5.6.2
- Fixed in
- 5.6.2
- Check
composer show statamic/cms
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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->emailThe 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
References
- https://github.com/statamic/cms/security/advisories/GHSA-qvpj-w7xj-r6w9
- https://nvd.nist.gov/vuln/detail/CVE-2024-36119
- https://github.com/statamic/cms/commit/0b804306c96c99b81755d5bd02df87ddf392853e
- https://dev.to/balogh08/cleaning-your-git-history-safely-removing-sensitive-data-10i5
- https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository
- https://github.com/advisories/GHSA-qvpj-w7xj-r6w9
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Composer (PHP) vulnerabilities
All Composer (PHP) entriesCVE-2026-64662
Statamic: Missing authorization on navigation endpoint allows disclosure of restricted entries
medium6.5Aug 6, 2026CVE-2026-64663
Statamic: Unsafe method invocation via Antlers template resolution allows data destruction
medium6.5Aug 6, 2026CVE-2026-64664
Statamic: Missing authorization on Control Panel endpoint allows disclosure of user existence
medium4.3Aug 6, 2026CVE-2026-64665
Statamic: Account takeover via OAuth email matching without email-verification check
high8.1Aug 6, 2026CVE-2026-71434
Statamic: Missing file upload validation on frontend forms allows uploading disallowed file types
medium5.3Aug 6, 2026CVE-2026-71435
Statamic: Stored Cross-Site Scripting in Automagic Form Notification Email Template
medium6.1Aug 6, 2026
