How severe is GHSA-qg7m-mwxm-j3h7?

GHSA-qg7m-mwxm-j3h7 has a CVSS score of 5.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-qg7m-mwxm-j3h7?

GHSA-qg7m-mwxm-j3h7 affects the following packages: zendframework/zend-developer-tools (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-qg7m-mwxm-j3h7?

Update zendframework/zend-developer-tools to 1.2.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qg7m-mwxm-j3h7 is resolved across your whole dependency graph.

How do I detect GHSA-qg7m-mwxm-j3h7 in my Packagist dependencies?

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

How do I mitigate GHSA-qg7m-mwxm-j3h7 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-qg7m-mwxm-j3h7?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-qg7m-mwxm-j3h7 can be triaged on real exposure rather than presence alone.

Is GHSA-qg7m-mwxm-j3h7 actively exploited in the wild?

No public exploit code has been indexed for GHSA-qg7m-mwxm-j3h7 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-qg7m-mwxm-j3h7 published, and has it been updated?

GHSA-qg7m-mwxm-j3h7 was published on June 7, 2024 and was last updated on December 4, 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

Not in CISA KEV

MEDIUM severity

GHSA-qg7m-mwxm-j3h7 — zendframework/zend-develo…

MEDIUMFix: zendframework/zend-developer-tools@ce27f46

GHSA-qg7m-mwxm-j3h7 is a medium-severity (CVSS 5.3) vulnerability in zendframework/zend-developer-tools. A fix is available for zendframework/zend-developer-tools — see the affected versions and patch details below.

Zend-developer-tools information disclosure vulnerability

Published

Jun 7, 2024

Updated

Dec 4, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Dec 4, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐘zendframework/zend-developer-tools

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

The package zendframework/zend-developer-tools provides a web-based toolbar for introspecting an application. When updating the package to support PHP 7.3, a change was made that could potentially prevent toolbar entries that are enabled by default from being disabled.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`zendframework/zend-developer-tools`	≥ 1.2.2&&< 1.2.3	1.2.3`composer require zendframework/zend-developer-tools:^1.2.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/zend-developer-tools, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update zendframework/zend-developer-tools to 1.2.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qg7m-mwxm-j3h7 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-qg7m-mwxm-j3h7 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-qg7m-mwxm-j3h7. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-qg7m-mwxm-j3h7 in your dependencies?

O3 Security finds GHSA-qg7m-mwxm-j3h7 across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works