GHSA-m24v-f7g5-gq67 CVE-2026-44306
Statamic CMS vulnerable to email enumeration via forgot password endpoint
- Severity
- 5.3 / 10
- Medium · CVSS 3.1
- Exploit chance (EPSS)
- 0.21%
- Chance of exploitation in the next 30 days. Higher than 10.71% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-204 Observable Response Discrepancy
- Fix
5.73.21- Upgrade statamic/cms to this version or later
Description
Impact
Responses from the forgot password forms hinted at whether an account existed for a given email address. An unauthenticated attacker could use this to enumerate valid users, which can aid in follow-up credential-based attacks.
Patches
This has been fixed in 5.73.21 and 6.15.0. The forgot password forms now return the same generic response regardless of whether the submitted email matches a registered user.
Affected versions
Packagist
| Package | Vulnerable | Fixed in |
|---|---|---|
| statamic/cms | < 5.73.21 |
5.73.21 |
| statamic/cms | >= 6.0.0, < 6.15.0 |
6.15.0 |
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.21
- composer
composer require statamic/cms:^5.73.21
Severity breakdown
CVSS 3.1 5.3
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
Weakness
CWE-204: Observable Response Discrepancy
The product provides different responses to incoming requests in a way that reveals internal state information to an unauthorized actor outside of the intended control sphere.
How to prevent it
- Architecture and Design: Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.
- Implementation: Ensure that error messages only contain minimal details that are useful to the intended audience and no one else. The messages need to strike the balance between being too cryptic (which can confuse users) or being too detailed (which may reveal more than intended). The messages should not reveal the methods that were used to determine the error. Attackers can use detailed information to refine or optimize their original attack, thereby increasing their chances of success. If errors must be captured in some detail, record them in log messages, but consider what could occur if the log messages can be viewed by attackers. Highly sensitive information such as passwords should never be saved to log files. Avoid inconsistent messaging that might accidentally tip off an attacker about internal state, such as whether a user account exists or not.
References
Advisories
Packages
Other links
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why 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 |
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