VulnerabilityPublished 11 Feb 2026Updated 12 Feb 2026

CVE-2026-25633: statamic cms · Missing Authorization

Affects statamic cmsSource CVE Database V5

Not known to be exploited · CVSS 4.3 Medium : upgrade to 6.2.5 or 5.73.6 when convenient.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score

4.3Medium

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

EPSS: 0.3% chance of exploitation in 30 days – higher than 24% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 6.2.5, 5.73.6

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
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: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within 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 11 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 statamic cms to 6.2.5 or 5.73.6.

Affected software

Product	Affected	Fixed in
statamiccms	Affected >=6.0.0-alpha.1 <6.2.5	Fixed in 6.2.5
statamiccms	Affected <5.73.6	Fixed in 5.73.6

AI-suggested

Organizations should upgrade Statamic CMS installations to version 5.73.6 or 6.2.5 or later, where the authorization checks have been properly implemented. Until upgrades can be applied, administrators should audit user permissions rigorously to ensure that only trusted users have control panel access and that asset viewing permissions are restricted appropriately. Implementing strong authentication mechanisms, such as multi-factor authentication, can reduce the risk of compromised accounts being used to exploit this flaw. Additionally, monitoring access logs for unusual asset download activity can help detect potential exploitation attempts. If possible, temporarily restricting asset access or disabling asset downloads for lower-privileged users can serve as a short-term mitigation. Regularly reviewing and updating CMS user roles and permissions is critical to minimizing exposure.

Description

Statamic is a, Laravel + Git powered CMS designed for building websites. Prior to 5.73.6 and 6.2.5, users without permission to view assets are able are able to download them and view their metadata. Logged-out users and users without permission to access the control panel are unable to take advantage of this. This has been fixed in 5.73.6 and 6.2.5.

Impact

The primary impact of this vulnerability is unauthorized disclosure of asset files and their metadata to users who should not have access. This can lead to leakage of sensitive information such as proprietary images, documents, or configuration files stored as assets within the CMS. While the vulnerability does not allow modification or deletion of assets, the confidentiality breach could facilitate further attacks or data exfiltration. Organizations relying on Statamic CMS for website content management may face reputational damage, compliance issues, or intellectual property loss if exploited. Since exploitation requires authenticated access with some control panel privileges, the risk is somewhat limited to insiders or compromised accounts. However, in environments with many users or weak access controls, the threat surface increases. The lack of known exploits suggests limited active targeting, but the vulnerability should be treated seriously given the potential for sensitive data exposure.

Summary

CVE-2026-25633 is a missing authorization vulnerability (CWE-862) in the Statamic content management system, which is built on Laravel and Git. The issue affects Statamic versions prior to 5.73.6 and 6.2.5, where users who are logged in and have some level of access to the control panel but lack explicit permission to view assets can still download those assets and view their metadata. This occurs because the system fails to properly enforce permission checks on asset access, allowing unauthorized disclosure of potentially sensitive files. However, unauthenticated users and those without control panel access cannot exploit this vulnerability. The flaw impacts confidentiality by exposing asset data but does not affect data integrity or system availability. The vulnerability was publicly disclosed in February 2026 and assigned a CVSS 3.1 base score of 4.3, reflecting a medium severity level. No known exploits have been observed in the wild, and patches were released in Statamic versions 5.73.6 and 6.2.5 to address the issue.

CWE-862Missing Authorization (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #4OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product does not perform an authorization check when an actor attempts to access a resource or perform an action.
Architecture and Design
Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries.
Architecture and Design
Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.8 (opens in a new tab)
V13.4.2 (opens in a new tab)
V7.2.2 (opens in a new tab)
Attack patterns
Exploitation of Thunderbolt Protection Flaws (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 19 Feb 2026, 13:53 UTC

WeaknessesCWE-862

Technical details

References

Community reviews

Related threats