Summary
Craft CMS: Incorrect path validation could potentially lead to path traversal
The ensurePathIsContained function of the Local file system class is theoretically vulnerable to path traversal, although no exploitable scenario has been discovered.
When a file is read, an Asset object uses the getFileStream method of the Volume where the asset file is stored, which in turn uses the getFileStream method of the file system class used by that Volume. For the Local file system, this function returns a stream to a file on the local disk after verifying and creating the correct file path.
The file path is constructed by first validating the path and then adding a prefix to the validated and normalized path. The prefix is the path to the local directory that houses the particular volume. The order of operations matters here: first, a validation step, afterward a normalization step, and finally the construction of the resulting file path. This opens the possibility of a desanitization-style vulnerability, where the normalization invalidates the assumptions made by the validation or sanitization that preceded it.
Impact
The issue is not directly exploitable, but for hardening, a fix is recommended regardless.
Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files. Typical impact: unauthorized file read or write outside the intended directory.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
craftcms/cms to 5.10.6 or later; craftcms/cms to 4.18.2 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is GHSA-7HXC-F267-H5Q7? GHSA-7HXC-F267-H5Q7 is a low-severity path traversal vulnerability in craftcms/cms (composer), affecting versions >= 5.0.0-RC1, < 5.10.6. It is fixed in 5.10.6, 4.18.2. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
- Which versions of craftcms/cms are affected by GHSA-7HXC-F267-H5Q7? craftcms/cms (composer) versions >= 5.0.0-RC1, < 5.10.6 is affected.
- Is there a fix for GHSA-7HXC-F267-H5Q7? Yes. GHSA-7HXC-F267-H5Q7 is fixed in 5.10.6, 4.18.2. Upgrade to this version or later.
- Is GHSA-7HXC-F267-H5Q7 exploitable, and should I be worried? Whether GHSA-7HXC-F267-H5Q7 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-7HXC-F267-H5Q7 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-7HXC-F267-H5Q7?
- Upgrade
craftcms/cmsto 5.10.6 or later - Upgrade
craftcms/cmsto 4.18.2 or later
- Upgrade