Skip to content

GHSA-jxq9-79vj-rgvw CVE-2026-27593

Statamic is vulnerable to account takeover via password reset link injection

High Packagist
Severity
9.3 / 10
High · CVSS 3.1
Exploit chance (EPSS)
0.52%
Chance of exploitation in the next 30 days. Higher than 44.18% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-640 Weak Password Recovery Mechanism for Forgotten Password
Fix
5.73.10
Upgrade statamic/cms to this version or later

Description

Impact

An attacker may leverage a vulnerability in the password reset feature to capture a user's token and reset the password on their behalf.

The attacker must know the email address of a valid account on the site, and the actual user must blindly click the link in their email even though they didn't request the reset.

Patches

This has been fixed in 6.7.1 and 5.73.10.

Note that a follow-up report showed the original 6.3.3 fix to be insufficient. The 5.73.10 fix was sufficient.

Affected versions

Packagist

PackageVulnerableFixed in
statamic/cms
< 5.73.10
5.73.10
statamic/cms
>= 6.0.0-alpha.1, < 6.7.1
6.7.1

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

statamic/cms Packagist → 5.73.10

composer
composer require statamic/cms:^5.73.10

Severity breakdown

CVSS 3.1 9.3

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

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
None

Weakness

CWE-640: Weak Password Recovery Mechanism for Forgotten Password

The product contains a mechanism for users to recover or change their passwords without knowing the original password, but the mechanism is weak.

How to prevent it
  • Architecture and Design: Make sure that all input supplied by the user to the password recovery mechanism is thoroughly filtered and validated.
  • Architecture and Design: Do not use standard weak security questions and use several security questions.
  • Architecture and Design: Make sure that there is throttling on the number of incorrect answers to a security question. Disable the password recovery functionality after a certain (small) number of incorrect guesses.
  • Architecture and Design: Require that the user properly answers the security question prior to resetting their password and sending the new password to the e-mail address of record.
  • Architecture and Design: Never allow the user to control what e-mail address the new password will be sent to in the password recovery mechanism.
  • Architecture and Design: Assign a new temporary password rather than revealing the original password.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-vx89-p3j7-8xqc
Statamic: Stored Cross-Site Scripting in Automagic Form Notification Email Template
Medium Also affects statamic/cms
GHSA-qhr7-v3xp-vw9m
Statamic: Missing file upload validation on frontend forms allows uploading disallowed file types
Medium Also affects statamic/cms
GHSA-qh8c-7588-qfrv
Statamic: Missing authorization on navigation endpoint allows disclosure of restricted entries
Medium Also affects statamic/cms
GHSA-j2vp-f2pv-5rj4
Statamic: Unsafe method invocation via Antlers template resolution allows data destruction
Medium Also affects statamic/cms
GHSA-93qh-5269-9wcf
Statamic: Account takeover via OAuth email matching without email-verification check
High Also affects statamic/cms
GHSA-225x-3jhx-wh4q
Statamic: Missing authorization on Control Panel endpoint allows disclosure of user existence
Medium Also affects statamic/cms
GHSA-jppw-r5j3-xf7x
Statamic CMS exposes two-factor recovery codes through dynamic Antlers rendering
Medium Also affects statamic/cms
GHSA-7mqq-4v55-88gh
Statamic CMS's incorrect authorization lets view-only users submit Live Preview content reserved for editors
Low Also affects statamic/cms
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor