CVE-2024-36119
What it is
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.
At a glance
- Exploitability
- Can be exploited locally on the machine with an admin-level account, but needs a user to act. Limited direct impact.
- Exploit odds
- 0.1% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.1% in the next 30 days (EPSS).
- Severity: 1.8 LOW (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.1% · EPSS, next 30 days
- Weakness
- CWE-312
- Record status
- Deferred
Attack profile CVSS 3.1 · 1.8
- Attack vector
- Local
- Complexity
- High
- Privileges needed
- High
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
Raw vector
CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:U/C:L/I:N/A:N
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2024-36119.md and follow it. Check whether this project is affected by CVE-2024-36119. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://github.com/statamic/cms/commit/0b804306c96c99b81755d5bd02df87ddf392853e
- https://github.com/statamic/cms/security/advisories/GHSA-qvpj-w7xj-r6w9
- https://github.com/statamic/cms/commit/0b804306c96c99b81755d5bd02df87ddf392853e
- https://github.com/statamic/cms/security/advisories/GHSA-qvpj-w7xj-r6w9
References
- 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/statamic/cms/commit/0b804306c96c99b81755d5bd02df87ddf392853e
- https://github.com/statamic/cms/security/advisories/GHSA-qvpj-w7xj-r6w9
- 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/statamic/cms/commit/0b804306c96c99b81755d5bd02df87ddf392853e
- https://github.com/statamic/cms/security/advisories/GHSA-qvpj-w7xj-r6w9