CVE-2026-33171
Arbitrary File Read in Statamic CMS Control Panel
Publication date: 2026-03-20
Last updated on: 2026-03-23
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| statamic | statamic | to 5.73.14 (exc) |
| statamic | statamic | From 6.0.0 (inc) to 6.7.0 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-22 | The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. |
Attack-Flow Graph
AI Powered Q&A
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, you should upgrade Statamic to version 5.73.14 or later, or version 6.7.0 or later, where the issue has been fixed.
Can you explain this vulnerability to me?
This vulnerability affects Statamic, a Laravel and Git powered content management system (CMS). Before versions 5.73.14 and 6.7.0, authenticated Control Panel users could exploit the system by manipulating the file dictionary's filename configuration parameter in the fieldtype's endpoint. This manipulation allowed them to read arbitrary files with extensions .json, .yaml, and .csv from the server.
The issue was fixed in versions 5.73.14 and 6.7.0.
How can this vulnerability impact me? :
This vulnerability allows authenticated users to read arbitrary .json, .yaml, and .csv files on the server. This could lead to unauthorized disclosure of sensitive configuration or data files, potentially exposing confidential information stored in these files.
However, the vulnerability does not allow modification or deletion of data, only reading (confidentiality impact).
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know