GHSA-jq87-2wxp-8349 is a high-severity (CVSS 7.5) vulnerability in zendframework/zendframework. A fix is available for zendframework/zendframework — see the affected versions and patch details below.
ZendFramework Route Parameter Injection Via Query String in `Zend\Mvc`
Real-World Exposure
zendframework/zendframework🐘zendframework/zendframeworkReal-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 Zend Framework 2, Zend\Mvc\Router\Http\Query is used primarily to allow appending query strings to URLs when assembled. However, due to the fact that it captures any query parameters into the RouteMatch, and the fact that RouteMatch parameters are merged with any parent routes, this can lead to overriding already captured routing parameters, bypassing constraints defined in the parents.
As an example, consider the following route definition:
array(
'user' => array(
'type' => 'segment',
'options' => array(
'route' => '/user/:key',
'defaults' => array(
'controller' => 'UserController',
'action' => 'show-action',
),
'constraints' => array(
'key' => '[a-z0-9]+',
),
),
'child_routes' => array(
'query' => array('type' => 'query'),
),
),
)
If the request URI was /user/foo/?controller=SecretController&key=invalid_value, the RouteMatch returned after routing would contain the following:
array(
'controller' => 'SecretController',
'action' => 'show-action',
'key' => 'invalid_value',
)
This would lead to execution of a different controller than intended, with a value for the key parameter that bypassed the constraints outlined in the parent route.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | zendframework/zendframework | ≥ 2.0.0&&< 2.0.8 | 2.0.8composer require zendframework/zendframework:^2.0.8 |
| 🐘Packagist | zendframework/zendframework | ≥ 2.1.0&&< 2.1.4 | 2.1.4composer require zendframework/zendframework:^2.1.4 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for zendframework/zendframework, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update zendframework/zendframework to 2.0.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jq87-2wxp-8349 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-jq87-2wxp-8349 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-jq87-2wxp-8349. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-jq87-2wxp-8349 in your dependencies?
O3 Security finds GHSA-jq87-2wxp-8349 across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.