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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

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

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-c43v-4cr8-6mvp?

O3 pinpoints whether GHSA-c43v-4cr8-6mvp is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

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.3%, placing it in the 26th 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 July 9, 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

GHSA-c43v-4cr8-6mvp

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

Also known asCVE-2026-56394

Published

Jul 9, 2026

Updated

Jul 9, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk26th percentile0.00%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

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
🐘Packagist	`craftcms/cms`	≥ 5.0.0-RC1&&< 5.9.13	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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-c43v-4cr8-6mvp is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-c43v-4cr8-6mvp. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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?

O3 detects GHSA-c43v-4cr8-6mvp across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works