Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-27593: CWE-640: Weak Password Recovery Mechanism for Forgotten Password in statamic cms

0
Critical
VulnerabilityCVE-2026-27593cvecve-2026-27593cwe-640
Published: Tue Feb 24 2026 (02/24/2026, 21:38:17 UTC)
Source: CVE Database V5
Vendor/Project: statamic
Product: cms

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.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 03/04/2026, 18:48:17 UTC

Technical Analysis

CVE-2026-27593 is a critical security vulnerability identified in the Statamic CMS, a Laravel and Git-powered content management system. The vulnerability stems from a weak password recovery mechanism (CWE-640) present in versions prior to 6.3.3 and 5.73.10. Specifically, an attacker who knows the email address of a valid user can initiate a password reset request. The system sends a reset link containing a token to the user's email. Due to insufficient protections, if the user clicks this link without having requested a reset, the attacker can capture the token and reset the password on the user's behalf, effectively taking over the account. This attack requires no prior authentication but does require user interaction (clicking the link). The vulnerability compromises both confidentiality and integrity by allowing unauthorized access and control over user accounts. The flaw has been addressed in Statamic versions 6.3.3 and 5.73.10 by strengthening the password reset workflow to prevent token capture and misuse. Although no active exploits have been reported, the vulnerability's CVSS score of 9.3 reflects its critical severity and potential for widespread impact. The vulnerability highlights the importance of secure token handling and user verification in password recovery processes.

Potential 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.

Mitigation Recommendations

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.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-02-20T19:43:14.601Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 699e1e91b7ef31ef0b4dd8db

Added to database: 2/24/2026, 9:56:33 PM

Last enriched: 3/4/2026, 6:48:17 PM

Last updated: 4/11/2026, 3:15:52 AM

Views: 286

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses