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-28424: CWE-862: Missing Authorization in statamic cms

0
Medium
VulnerabilityCVE-2026-28424cvecve-2026-28424cwe-862
Published: Fri Feb 27 2026 (02/27/2026, 22:14:01 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 5.73.11 and 6.4.0, user email addresses were included in responses from the user fieldtype’s data endpoint for control panel users who did not have the "view users" permission. This has been fixed in 5.73.11 and 6.4.0.

AI-Powered Analysis

AILast updated: 02/27/2026, 22:48:57 UTC

Technical Analysis

CVE-2026-28424 is a security vulnerability classified under CWE-862 (Missing Authorization) affecting the Statamic content management system (CMS), which is built on Laravel and integrates Git for content management. The flaw exists in versions prior to 5.73.11 and between 6.0.0 and 6.4.0, where the user fieldtype’s data endpoint improperly includes email addresses of control panel users in its responses. This occurs even when the requesting user lacks the 'view users' permission, indicating a failure in enforcing proper authorization checks. The vulnerability allows authenticated users with limited privileges to access sensitive user email information, potentially enabling targeted phishing, social engineering, or further reconnaissance attacks. The vulnerability does not allow modification of data or disruption of service, thus impacting confidentiality but not integrity or availability. The issue was addressed and fixed in Statamic versions 5.73.11 and 6.4.0 by enforcing correct permission checks on the data endpoint. No public exploits have been reported to date, but the vulnerability's presence in a popular CMS component makes it a notable risk for organizations relying on affected versions.

Potential Impact

The primary impact of CVE-2026-28424 is the unauthorized disclosure of control panel user email addresses, which compromises user confidentiality. This exposure can facilitate targeted phishing campaigns, spear-phishing, or social engineering attacks against administrative or privileged users, potentially leading to further compromise of organizational systems. While the vulnerability does not allow direct modification of data or denial of service, the leakage of sensitive user information can be a stepping stone for attackers to escalate privileges or gain unauthorized access through secondary attacks. Organizations using affected Statamic CMS versions face increased risk of user-targeted attacks, especially if email addresses are linked to critical administrative accounts. The vulnerability requires authenticated access with low privileges, which somewhat limits exposure but does not eliminate risk, particularly in environments with many users or where credentials may be shared or compromised. The absence of known exploits reduces immediate risk but does not preclude future exploitation.

Mitigation Recommendations

To mitigate CVE-2026-28424, organizations should promptly upgrade Statamic CMS to versions 5.73.11 or 6.4.0 or later, where the authorization checks have been properly implemented. Until upgrades can be applied, administrators should restrict access to the control panel and limit user accounts to only those necessary, minimizing the number of users with any authenticated access. Implement strict role-based access controls and audit user permissions regularly to ensure no unnecessary privileges are granted. Monitoring access logs for unusual or unauthorized access attempts to the user fieldtype’s data endpoint can help detect exploitation attempts. Additionally, organizations should educate users about phishing risks, as leaked email addresses may be used in targeted attacks. Network-level controls such as web application firewalls (WAFs) can be configured to detect and block suspicious requests to the vulnerable endpoint. Finally, consider implementing multi-factor authentication (MFA) for all control panel users to reduce the risk of credential compromise.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-02-27T15:54:05.136Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 69a21f2232ffcdb8a27f4a8c

Added to database: 2/27/2026, 10:48:02 PM

Last enriched: 2/27/2026, 10:48:57 PM

Last updated: 2/28/2026, 12:50:21 AM

Views: 6

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 in Console -> Billing 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