CVE-2024-36119

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

LOW
1.8
CVSS Score
Published: May 30, 2024 at 08:57 PM UTC
Updated: June 17, 2026 at 07:36 AM UTC
1 product affected across 1 vendorStatamic

Using cms by statamic?

Get instant alerts when new vulnerabilities affect cms - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
LOW1.8
Exploit prediction
EPSS 0.1%
SSVC
No known exploit

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 5.6.2
Affected range stops below 5.6.2, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

1.8LOWGitHub_M
Attack Vector
LOCAL
Complexity
HIGH
Privileges
HIGH
User Interaction
REQUIRED
Scope
UNCHANGED
Confidentiality
LOW
Integrity
NONE
Availability
NONE
Vector?

Quick Info

StatusDEFERRED
CWE
CWE-312

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card