How severe is GHSA-c43v-4cr8-6mvp?

No CVSS score has been assigned to GHSA-c43v-4cr8-6mvp yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-c43v-4cr8-6mvp?

GHSA-c43v-4cr8-6mvp affects the following packages: craftcms/cms (Packagist), craftcms/cms (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-c43v-4cr8-6mvp?

Update craftcms/cms to 4.17.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-c43v-4cr8-6mvp is resolved across your whole dependency graph.

How do I detect GHSA-c43v-4cr8-6mvp in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for craftcms/cms, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-c43v-4cr8-6mvp if there is no patch (or I can't update yet)?

Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Is GHSA-c43v-4cr8-6mvp actively exploited in the wild?

No public exploit code has been indexed for GHSA-c43v-4cr8-6mvp yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-c43v-4cr8-6mvp?

GHSA-c43v-4cr8-6mvp has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 40th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-c43v-4cr8-6mvp?

GHSA-c43v-4cr8-6mvp is classified as Path Traversal (CWE-22). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-c43v-4cr8-6mvp published, and has it been updated?

GHSA-c43v-4cr8-6mvp was published on July 9, 2026 and was last updated on August 6, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

Not in CISA KEV

GHSA-c43v-4cr8-6mvp — craftcms/cms

Fix: craftcms/cms@30f5f1a

GHSA-c43v-4cr8-6mvp is a Path Traversal vulnerability in craftcms/cms. A fix is available for craftcms/cms — see the affected versions and patch details below.

Craft CMS has authenticated path traversal in `assets/icon`, allowing local `.svg` file read

Also known asCVE-2026-56394

Published

Jul 9, 2026

Updated

Aug 6, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Oct 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-c43v-4cr8-6mvp.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs40th percentile — riskier than 40% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

2 pkgs affected

🐘craftcms/cms🐘craftcms/cms

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

Summary

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-1123
actionIcon(string $extension) calls Assets::iconPath($extension) and returns sendFile($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().

Impact

Authenticated users can read local .svg files accessible to the application process.

References

https://github.com/craftcms/cms/commit/30f5f1a8d6edf0f3a00be72c42c78d9dc7d72d5c

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`craftcms/cms`	≥ 4.0.0-RC1&&< 4.17.7	4.17.7`composer require craftcms/cms:^4.17.7`
🐘Packagist	`craftcms/cms`	≥ 5.0.0-RC1&&< 5.9.13	5.9.13`composer require craftcms/cms:^5.9.13`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for craftcms/cms, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update craftcms/cms to 4.17.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-c43v-4cr8-6mvp is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Frequently Asked Questions

### Summary 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-1123` - `actionIcon(string $extension)` calls `Assets::iconPath($extension)` and returns `sendFile($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: -

O3 Security · Impact-Aware SCA

Is GHSA-c43v-4cr8-6mvp in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works