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

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

1.8 · CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:U/C:L/I:N/A:N

EPSS

• CVE-2024-36119: 0.14% estimated exploitation activity in the next 30 days; percentile 3.16 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Users registering via the user:registerform tag will have their password confirmation stored in plain text in their user file. Impact This only affects sites matching all of the following conditions: - Running Statamic versions between 5.3.0 and 5.6.1. (This version range represents only one calendar week) - Using the user:registerform tag. - Using file-based user accounts. (Does not affect users stored in a database.) - Has users that have registered during that time period. (Existing users are not affected.) The password is only visible to users that have access to read user yaml files, typically developers of the application itself. Patches The issue has been patched in 5.6.2, however any users registered during that time period and using the affected version range will still have the the passwordconfirmation value in their yaml files. We recommend that affected users have their password reset. The following query can be entered into php artisan tinker and will output a list of…

Published by the source

2 Jun 2024, 22:30 UTC

Last modified by the source

2 Jun 2024, 22:30 UTC

Source last checked

26 Oct 2026, 14:25 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-qvpj-w7xj-r6w9

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-36119

Advisory: Password confirmation stored in plain text via registration form in statamic/cms
IDs: CVE-2024-36119, GHSA-qvpj-w7xj-r6w9
Record: https://patchnext.com/advisories/cve-2024-36119 (revision 1, source checked 26 Oct 2026, 14:25 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 1.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: statamic/cms 5.6.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist statamic/cms: affected >= 5.3.0, < 5.6.2; fixed in 5.6.2

## Suggested inspection (read-only)
- Packagist statamic/cms: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on statamic/cms.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-qvpj-w7xj-r6w9 (GitHub-reviewed advisory GHSA-qvpj-w7xj-r6w9 lists affected ranges: Packagist statamic/cms >=5.3.0 <5.6.2)

Commands are suggestions: review each one before running it.