VulnerabilityPublished 24 Feb 2026Updated 27 Feb 2026

CVE-2026-27593: statamic cms · Weak Password Recovery

Affects statamic cmsSource CVE Database V5

Not known to be exploited · CVSS 9.3 Critical : upgrade to 6.3.3 or 5.73.10 as a priority.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

9.3Critical

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.5% chance of exploitation in 30 days – higher than 43% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 6.3.3, 5.73.10

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

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 24 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade cms to 6.3.3 or 5.73.10; statamic/cms to 5.73.10.

Affected software

Product	Affected	Fixed in
statamiccms	Affected >=6.0.0-alpha.1 <6.3.3	Fixed in 6.3.3
statamiccms	Affected <5.73.10	Fixed in 5.73.10
GitHubstatamic/cms`pkg:github/statamic/cms`Other threats	Affected <5.73.10	Fixed in 5.73.10

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2026-27593, organizations should immediately upgrade Statamic CMS to versions 6.3.3 or 5.73.10 or later, where the vulnerability is fixed. In addition, administrators should implement multi-factor authentication (MFA) to reduce the impact of compromised credentials. Educate users to be cautious of unsolicited password reset emails and verify the legitimacy of such requests before clicking links. Implement email filtering and anti-phishing controls to reduce the risk of malicious emails reaching users. Where possible, customize the password reset workflow to include additional verification steps, such as secondary confirmation via SMS or security questions. Monitor logs for unusual password reset activity and failed login attempts to detect potential exploitation attempts. Finally, review and tighten email server configurations to prevent spoofing and ensure secure delivery of password reset emails.

Description

Statmatic is a Laravel and Git powered content management system (CMS). Prior to versions 6.3.3 and 5.73.10, 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. This has been fixed in 6.3.3 and 5.73.10.

Impact

The impact of CVE-2026-27593 is significant for organizations using vulnerable versions of Statamic CMS. Successful exploitation allows attackers to hijack user accounts by resetting passwords without authorization, leading to unauthorized access to sensitive content and administrative functions. This can result in data breaches, content defacement, and potential lateral movement within the affected environment. Since the vulnerability affects password recovery, it undermines user trust and can facilitate further attacks such as privilege escalation or persistent access. The requirement for user interaction (clicking a malicious link) somewhat limits automated exploitation but social engineering can easily overcome this barrier. The vulnerability does not affect availability directly but severely compromises confidentiality and integrity. Organizations relying on Statamic CMS for public-facing or internal websites are at risk, especially those with high-value or sensitive data. The lack of known exploits in the wild suggests a window for proactive patching before widespread abuse occurs.

CWE-640Weak Password Recovery Mechanism for Forgotten Password (opens in a new tab)
Base weaknessLikelihood of exploit: HighOWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
The product contains a mechanism for users to recover or change their passwords without knowing the original password, but the mechanism is weak.
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.
OWASP Cheat Sheets
Choosing and Using Security Questions (opens in a new tab)
Forgot Password (opens in a new tab)
OWASP Authentication (opens in a new tab)
OWASP ASVS 4.0.3
V2.5.3 (opens in a new tab)
V2.5.2 (opens in a new tab)
V2.5.1 (opens in a new tab)
Attack patterns
Password Recovery Exploitation (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 4 Mar 2026, 18:48 UTC

WeaknessesCWE-640

Technical details

References

Community reviews

Related threats