How severe is GHSA-53vf-c43h-j2x9?

No CVSS score has been assigned to GHSA-53vf-c43h-j2x9 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-53vf-c43h-j2x9?

GHSA-53vf-c43h-j2x9 affects the following packages: craftcms/cms (Packagist), craftcms/cms (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-53vf-c43h-j2x9?

Update craftcms/cms to 5.8.21 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-53vf-c43h-j2x9 is resolved across your whole dependency graph.

How do I detect GHSA-53vf-c43h-j2x9 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-53vf-c43h-j2x9 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-53vf-c43h-j2x9?

O3 pinpoints whether GHSA-53vf-c43h-j2x9 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-53vf-c43h-j2x9 actively exploited in the wild?

No public exploit code has been indexed for GHSA-53vf-c43h-j2x9 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 type of vulnerability is GHSA-53vf-c43h-j2x9?

GHSA-53vf-c43h-j2x9 is classified as Information Exposure (CWE-200). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-53vf-c43h-j2x9 published, and has it been updated?

GHSA-53vf-c43h-j2x9 was published on January 5, 2026 and was last updated on February 3, 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-53vf-c43h-j2x9

Fix: craftcms/cms@4bcb0db

GHSA-53vf-c43h-j2x9 is a Information Exposure vulnerability in craftcms/cms. O3 Security confirms whether GHSA-53vf-c43h-j2x9 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Craft CMS vulnerable to potential information disclosure via unchecked asset relocation

Also known asCVE-2025-68436

Published

Jan 5, 2026

Updated

Feb 3, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Feb 3, 2026 · OSV.dev, NVD, 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

Authenticated users on a Craft installation could potentially expose sensitive assets via their user profile photo via maliciously crafted requests.

Users should update to the patched versions (5.8.21 and 4.16.17) to mitigate the issue.

Resources:

https://github.com/craftcms/cms/commit/4bcb0db554e273b66ce3b75263a13414c2368fc9

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`craftcms/cms`	≥ 5.0.0-RC1&&< 5.8.21	5.8.21
🐘Packagist	`craftcms/cms`	≥ 4.0.0-RC1&&< 4.16.17	4.16.17

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 5.8.21 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-53vf-c43h-j2x9 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-53vf-c43h-j2x9 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-53vf-c43h-j2x9. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Authenticated users on a Craft installation could potentially expose sensitive assets via their user profile photo via maliciously crafted requests. Users should update to the patched versions (5.8.21 and 4.16.17) to mitigate the issue. Resources: https://github.com/craftcms/cms/commit/4bcb0db554e273b66ce3b75263a13414c2368fc9 https://github.com/craftcms/cms/commit/4bcb0db554e273b66ce3b75263a13414c2368fc9

O3 Security · Impact-Aware SCA

Is GHSA-53vf-c43h-j2x9 in your dependencies?

O3 detects GHSA-53vf-c43h-j2x9 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