How severe is GHSA-w5mj-j45q-m638?

No CVSS score has been assigned to GHSA-w5mj-j45q-m638 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-w5mj-j45q-m638?

GHSA-w5mj-j45q-m638 affects the following packages: zendframework/zendframework1 (Packagist), zendframework/zendframework1 (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-w5mj-j45q-m638?

Update zendframework/zendframework1 to 1.9.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w5mj-j45q-m638 is resolved across your whole dependency graph.

How do I detect GHSA-w5mj-j45q-m638 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for zendframework/zendframework1. 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-w5mj-j45q-m638 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-w5mj-j45q-m638?

O3 pinpoints whether GHSA-w5mj-j45q-m638 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-w5mj-j45q-m638 actively exploited in the wild?

No public exploit code has been indexed for GHSA-w5mj-j45q-m638 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.

When was GHSA-w5mj-j45q-m638 published, and has it been updated?

GHSA-w5mj-j45q-m638 was published on June 7, 2024. 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-w5mj-j45q-m638

ZendFramework1 Potential Security Issues in Bundled Dojo Library

Published

Jun 7, 2024

Updated

Jun 7, 2024

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Blast Radius

2 pkgs affected

🐘zendframework/zendframework1🐘zendframework/zendframework1

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

In mid-March, 2010, the Dojo Foundation issued a Security Advisory indicating potential security issues with specific files in Dojo Toolkit. Details of the advisory may be found on the Dojo website:

http://dojotoolkit.org/blog/post/dylan/2010/03/dojo-security-advisory/ In particular, several files in the Dojo tree were identified as having potential exploits, and the Dojo team also advised disabling or removing any PHP scripts in the tree when deploying to production.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`zendframework/zendframework1`	≥ 1.9.0&&< 1.9.8	1.9.8
🐘Packagist	`zendframework/zendframework1`	≥ 1.10.0&&< 1.10.3	1.10.3

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for zendframework/zendframework1. 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 zendframework/zendframework1 to 1.9.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w5mj-j45q-m638 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-w5mj-j45q-m638 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-w5mj-j45q-m638. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

In mid-March, 2010, the Dojo Foundation issued a Security Advisory indicating potential security issues with specific files in Dojo Toolkit. Details of the advisory may be found on the Dojo website: http://dojotoolkit.org/blog/post/dylan/2010/03/dojo-security-advisory/ In particular, several files in the Dojo tree were identified as having potential exploits, and the Dojo team also advised disabling or removing any PHP scripts in the tree when deploying to production.

O3 Security · Impact-Aware SCA

Is GHSA-w5mj-j45q-m638 in your dependencies?

O3 detects GHSA-w5mj-j45q-m638 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