CVE-2024-36119 is a low-severity (CVSS 1.8) CWE-312 vulnerability in statamic/cms. A fix is available for statamic/cms — see the affected versions and patch details below.
Password confirmation stored in plain text via registration form in statamic/cms
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2024-36119.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
statamic/cmsReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | statamic/cms | ≥ 5.3.0&&< 5.6.2 | 5.6.2composer require statamic/cms:^5.6.2 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for statamic/cms, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update statamic/cms to 5.6.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-36119 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Frequently Asked Questions
Is CVE-2024-36119 in your dependencies?
Find it across Packagist, including transitive dependencies.