Password confirmation stored in plain text via registration form in statamic/cms
Key facts
- Attack vector
- Local
- Privileges required
- High
- User interaction
- Required
- Attack complexity
- High
- Impact type
- Information disclosure
- Confidentiality · integrity · availability
- Low · None · None
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA and GitHub. Impact type from CWE-312.
Summary
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.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| statamic | cms | 5.3.0 to before 5.6.2 | 5.6.2 | Patch available | CNA |
| — | statamic/cms (Packagist) | 5.3.0 to before 5.6.2 | 5.6.2 | Patch available | GHSA-qvpj-w7xj-r6w9 |
- cms Vendorstatamic Affected 5.3.0 to before 5.6.2 Fixed in 5.6.2 Patch available CNA
- statamic/cms (Packagist) Vendor— Affected 5.3.0 to before 5.6.2 Fixed in 5.6.2 Patch available GHSA-qvpj-w7xj-r6w9
Remediation
- Fix · CNA cms (statamic) Fixed in 5.6.2
- Fix · GHSA-qvpj-w7xj-r6w9 statamic/cms (Packagist) Fixed in 5.6.2 Advisory →
Timeline
- 2026-10-02 Threatist record created from CVE-2024-36119
- 2026-10-03 Alias added: GHSA-qvpj-w7xj-r6w9
References
Other 5
- 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
- https://github.com/statamic/cms
More statamic vulnerabilities
- TI-2024-16191 Statamic account takeover via XSS and password reset link CVSS 3.1HIGH 8.2
- TI-2023-18622 Statamic's Antlers sanitizer cannot effectively sanitize malicious SVG CVSS 3.1MEDIUM 5.5
- TI-2021-20500 A Code Execution vulnerability exists in Statamic Version through 3.2.26 via… CVSS 3.1CRITICAL 9.8
- TI-2023-25469 Statamic CMS remote code execution via front-end form uploads CVSS 3.1CRITICAL 9.8
- TI-2023-26081 Remote code execution via form uploads in statamic/cms CVSS 3.1HIGH 8.8
- TI-2026-21980 Statamic is vulnerable to account takeover via password reset link injection CVSS 3.1CRITICAL 9.3
Sources
- CVE-2024-36119 · CVE Program
- CVE-2024-36119 · NVD
- FIRST EPSS
- GHSA-qvpj-w7xj-r6w9 · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences