Summary
Craft CMS has authenticated path traversal in assets/icon, allowing local .svg file read
An authenticated path traversal in assets/icon allows local SVG file read by passing traversal sequences in the extension parameter. The issue is caused by file existence checks happening before extension validation.
Details
The endpoint:
src/controllers/AssetsController.php:1115-1123actionIcon(string $extension)callsAssets::iconPath($extension)and returnssendFile($path, ...).
In Assets::iconPath():
- Path is built from user-controlled
extension:src/helpers/Assets.php:906-909
- If
file_exists($path)is true, path is returned immediately:src/helpers/Assets.php:910-912
Validation exists in Assets::iconSvg():
preg_match('/^\w+$/', $extension)src/helpers/Assets.php:927-931
However, that validation is only reached if iconPath() does not find a file.
So traversal payloads that resolve to existing .svg files bypass validation and are served by sendFile().
References
Impact
- Authenticated users can read local .svg files accessible to the application process.
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 4.17.7 or later; craftcms/cms to 5.9.13 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is GHSA-C43V-4CR8-6MVP? GHSA-C43V-4CR8-6MVP is a low-severity path traversal vulnerability in craftcms/cms (composer), affecting versions >= 4.0.0-RC1, <= 4.17.6. It is fixed in 4.17.7, 5.9.13. 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-C43V-4CR8-6MVP? craftcms/cms (composer) versions >= 4.0.0-RC1, <= 4.17.6 is affected.
- Is there a fix for GHSA-C43V-4CR8-6MVP? Yes. GHSA-C43V-4CR8-6MVP is fixed in 4.17.7, 5.9.13. Upgrade to this version or later.
- Is GHSA-C43V-4CR8-6MVP exploitable, and should I be worried? Whether GHSA-C43V-4CR8-6MVP 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-C43V-4CR8-6MVP 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-C43V-4CR8-6MVP?
- Upgrade
craftcms/cmsto 4.17.7 or later - Upgrade
craftcms/cmsto 5.9.13 or later
- Upgrade