CVE-2024-36119

Password confirmation stored in plain text via registration form in statamic/cms

Users registering via the user:register_form tag will have their password confirmation stored in plain text in their user file.

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

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_form tag.
• 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.

CVE-2024-36119 has a CVSS score of 1.8 (Low). The vector is requires local access, high privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (5.6.2); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

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());

1. What is CVE-2024-36119? CVE-2024-36119 is a low-severity security vulnerability in statamic/cms (composer), affecting versions >= 5.3.0, < 5.6.2. It is fixed in 5.6.2.
2. How severe is CVE-2024-36119? CVE-2024-36119 has a CVSS score of 1.8 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of statamic/cms are affected by CVE-2024-36119? statamic/cms (composer) versions >= 5.3.0, < 5.6.2 is affected.
4. Is there a fix for CVE-2024-36119? Yes. CVE-2024-36119 is fixed in 5.6.2. Upgrade to this version or later.
5. Is CVE-2024-36119 exploitable, and should I be worried? Whether CVE-2024-36119 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2024-36119 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2024-36119? Upgrade statamic/cms to 5.6.2 or later.

Other vulnerabilities in statamic/cms