GHSA-JQ87-2WXP-8349

GHSA-JQ87-2WXP-8349 is a high-severity security vulnerability in zendframework/zendframework (composer), affecting versions >= 2.0.0, < 2.0.8. It is fixed in 2.0.8, 2.1.4.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

ZendFramework Route Parameter Injection Via Query String in Zend\Mvc

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.

Impact

GHSA-JQ87-2WXP-8349 has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.0.8, 2.1.4); upgrading removes the vulnerable code path.

Affected versions

zendframework/zendframework (>= 2.0.0, < 2.0.8) zendframework/zendframework (>= 2.1.0, < 2.1.4)

Security releases

zendframework/zendframework → 2.0.8 (composer) zendframework/zendframework → 2.1.4 (composer)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environmentNew to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

zendframework/zendframework to 2.0.8 or later; zendframework/zendframework to 2.1.4 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

  1. What is GHSA-JQ87-2WXP-8349? GHSA-JQ87-2WXP-8349 is a high-severity security vulnerability in zendframework/zendframework (composer), affecting versions >= 2.0.0, < 2.0.8. It is fixed in 2.0.8, 2.1.4.
  2. How severe is GHSA-JQ87-2WXP-8349? GHSA-JQ87-2WXP-8349 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
  3. Which versions of zendframework/zendframework are affected by GHSA-JQ87-2WXP-8349? zendframework/zendframework (composer) versions >= 2.0.0, < 2.0.8 is affected.
  4. Is there a fix for GHSA-JQ87-2WXP-8349? Yes. GHSA-JQ87-2WXP-8349 is fixed in 2.0.8, 2.1.4. Upgrade to this version or later.
  5. Is GHSA-JQ87-2WXP-8349 exploitable, and should I be worried? Whether GHSA-JQ87-2WXP-8349 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
  6. What actually determines whether GHSA-JQ87-2WXP-8349 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
  7. How do I fix GHSA-JQ87-2WXP-8349?
    • Upgrade zendframework/zendframework to 2.0.8 or later
    • Upgrade zendframework/zendframework to 2.1.4 or later

Other vulnerabilities in zendframework/zendframework

Stop the waste.
Protect your environment with Kodem.