CVE-2026-33171: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in statamic cms
Statamic is a Laravel and Git powered content management system (CMS). Prior to versions 5.73.14 and 6.7.0, authenticated Control Panel users could read arbitrary `.json`, `.yaml`, and `.csv` files from the server by manipulating the file dictionary's `filename` configuration parameter in the fieldtype's endpoint. This has been fixed in 5.73.14 and 6.7.0.
AI Analysis
Technical Summary
CVE-2026-33171 is a path traversal vulnerability identified in the Statamic content management system (CMS), which is built on Laravel and Git technologies. The flaw exists in the handling of the file dictionary's filename configuration parameter within the fieldtype's endpoint. Specifically, authenticated users with Control Panel access can manipulate this parameter to traverse directories and read arbitrary files with extensions such as .json, .yaml, and .csv from the server filesystem. This occurs due to improper limitation of pathname to a restricted directory (CWE-22), allowing attackers to bypass intended directory restrictions. The vulnerability affects Statamic versions prior to 5.73.14 and 6.7.0. Exploitation requires valid authentication credentials but does not require additional user interaction. The vulnerability impacts confidentiality by exposing potentially sensitive configuration or data files but does not affect integrity or availability. The CVSS v3.1 base score is 4.3, reflecting network attack vector, low attack complexity, required privileges, no user interaction, and limited confidentiality impact. No public exploits have been reported to date. The vendor has addressed the issue in versions 5.73.14 and 6.7.0 by properly restricting pathname traversal in the affected endpoint.
Potential Impact
The primary impact of CVE-2026-33171 is unauthorized disclosure of sensitive information stored in .json, .yaml, and .csv files on servers running vulnerable Statamic CMS versions. Attackers with authenticated Control Panel access can leverage this flaw to read configuration files, credentials, or other sensitive data, potentially facilitating further attacks such as privilege escalation or lateral movement. Although the vulnerability does not allow modification or deletion of files, the confidentiality breach can expose internal system details and user data. Organizations relying on Statamic CMS for website or application content management may face increased risk of data leakage, especially if sensitive information is stored in accessible file formats. The requirement for authentication limits the attack surface to insiders or compromised accounts, but the ease of exploitation and network accessibility raise concerns for organizations with weak access controls or exposed Control Panels. No known active exploitation reduces immediate risk, but delayed patching could lead to targeted attacks. Overall, the vulnerability poses a moderate threat to confidentiality and organizational security posture.
Mitigation Recommendations
To mitigate CVE-2026-33171, organizations should promptly upgrade Statamic CMS to versions 5.73.14 or 6.7.0, where the vulnerability has been fixed. Until upgrades are applied, administrators should restrict Control Panel access strictly to trusted users and enforce strong authentication mechanisms such as multi-factor authentication (MFA) to reduce the risk of credential compromise. Network-level controls like IP whitelisting or VPN access for the Control Panel can further limit exposure. Review and audit file permissions on the server to ensure sensitive files are not unnecessarily accessible to the web server process. Implement monitoring and alerting for unusual file access patterns or Control Panel activities that could indicate exploitation attempts. Additionally, consider scanning existing systems for signs of unauthorized file reads or suspicious behavior. Regularly update and patch all components of the CMS and underlying infrastructure to minimize exposure to known vulnerabilities.
Affected Countries
United States, United Kingdom, Canada, Australia, Germany, Netherlands, France, Sweden, New Zealand, Ireland
CVE-2026-33171: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in statamic cms
Description
Statamic is a Laravel and Git powered content management system (CMS). Prior to versions 5.73.14 and 6.7.0, authenticated Control Panel users could read arbitrary `.json`, `.yaml`, and `.csv` files from the server by manipulating the file dictionary's `filename` configuration parameter in the fieldtype's endpoint. This has been fixed in 5.73.14 and 6.7.0.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-33171 is a path traversal vulnerability identified in the Statamic content management system (CMS), which is built on Laravel and Git technologies. The flaw exists in the handling of the file dictionary's filename configuration parameter within the fieldtype's endpoint. Specifically, authenticated users with Control Panel access can manipulate this parameter to traverse directories and read arbitrary files with extensions such as .json, .yaml, and .csv from the server filesystem. This occurs due to improper limitation of pathname to a restricted directory (CWE-22), allowing attackers to bypass intended directory restrictions. The vulnerability affects Statamic versions prior to 5.73.14 and 6.7.0. Exploitation requires valid authentication credentials but does not require additional user interaction. The vulnerability impacts confidentiality by exposing potentially sensitive configuration or data files but does not affect integrity or availability. The CVSS v3.1 base score is 4.3, reflecting network attack vector, low attack complexity, required privileges, no user interaction, and limited confidentiality impact. No public exploits have been reported to date. The vendor has addressed the issue in versions 5.73.14 and 6.7.0 by properly restricting pathname traversal in the affected endpoint.
Potential Impact
The primary impact of CVE-2026-33171 is unauthorized disclosure of sensitive information stored in .json, .yaml, and .csv files on servers running vulnerable Statamic CMS versions. Attackers with authenticated Control Panel access can leverage this flaw to read configuration files, credentials, or other sensitive data, potentially facilitating further attacks such as privilege escalation or lateral movement. Although the vulnerability does not allow modification or deletion of files, the confidentiality breach can expose internal system details and user data. Organizations relying on Statamic CMS for website or application content management may face increased risk of data leakage, especially if sensitive information is stored in accessible file formats. The requirement for authentication limits the attack surface to insiders or compromised accounts, but the ease of exploitation and network accessibility raise concerns for organizations with weak access controls or exposed Control Panels. No known active exploitation reduces immediate risk, but delayed patching could lead to targeted attacks. Overall, the vulnerability poses a moderate threat to confidentiality and organizational security posture.
Mitigation Recommendations
To mitigate CVE-2026-33171, organizations should promptly upgrade Statamic CMS to versions 5.73.14 or 6.7.0, where the vulnerability has been fixed. Until upgrades are applied, administrators should restrict Control Panel access strictly to trusted users and enforce strong authentication mechanisms such as multi-factor authentication (MFA) to reduce the risk of credential compromise. Network-level controls like IP whitelisting or VPN access for the Control Panel can further limit exposure. Review and audit file permissions on the server to ensure sensitive files are not unnecessarily accessible to the web server process. Implement monitoring and alerting for unusual file access patterns or Control Panel activities that could indicate exploitation attempts. Additionally, consider scanning existing systems for signs of unauthorized file reads or suspicious behavior. Regularly update and patch all components of the CMS and underlying infrastructure to minimize exposure to known vulnerabilities.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-03-17T22:16:36.718Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 69bdc1299e4ece4ed25050a2
Added to database: 3/20/2026, 9:50:33 PM
Last enriched: 3/20/2026, 9:51:58 PM
Last updated: 3/21/2026, 2:05:14 AM
Views: 13
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
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
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.