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

> Statamic CMS stores password confirmations in plain text in user files when using specific registration forms and file-based accounts, exposing credentials to developers.

- **Severity:** Low 1.8 (`CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 30 May 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-qvpj-w7xj-r6w9

## What is CVE-2024-36119?

CVE-2024-36119 is a low-severity vulnerability in statamic cms, published on 30 May 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official 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.

Weakness: CWE-312 (Cleartext Storage of Sensitive Information)

## Which versions are affected by CVE-2024-36119?

2 open source packages ship an affected version, including statamic/cms.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `statamic/cms` | Packagist | From 5.3.0 | 5.6.2 |
| `statamic/cms` | Packagist | From 5.3.0 | 5.6.2 |

## How do I fix CVE-2024-36119?

Upgrade statamic/cms to 5.6.2 or later.

## Is CVE-2024-36119 being exploited?

There is no known exploitation of CVE-2024-36119 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-36119 and fix it if it is affected.

What it is: CVE-2024-36119 is a low-severity vulnerability in statamic cms, published on 30 May 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-36119 in the wild and no public exploit code.

Affected packages and fixed versions:
- statamic/cms (Packagist): affected from 5.3.0; fixed in 5.6.2
- statamic/cms (Packagist): affected from 5.3.0; fixed in 5.6.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-36119/ (Markdown: https://insights.sbomify.com/CVE-2024-36119/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-36119
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-36119
- OSV: https://osv.dev/vulnerability/CVE-2024-36119

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-36119/
Summaries are generated and may contain mistakes; the official description above is the record.