GHSA-JMMP-VH96-78RM

Zend-Feed URL Rewrite vulnerability

zend-diactoros (and, by extension, Expressive), zend-http (and, by extension, Zend Framework MVC projects), and zend-feed (specifically, its PubSubHubbub sub-component) each contain a potential URL rewrite exploit. In each case, marshaling a request URI includes logic that introspects HTTP request headers that are specific to a given server-side URL rewrite mechanism.

When these headers are present on systems not running the specific URL rewriting mechanism, the logic would still trigger, allowing a malicious client or proxy to emulate the headers to request arbitrary content.

A victim's authenticated browser session is used to submit forged requests to an application that cannot distinguish them from legitimate ones. Typical impact: state-changing actions performed as the victim without their consent.

GHSA-JMMP-VH96-78RM 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.10.3); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

1. What is GHSA-JMMP-VH96-78RM? GHSA-JMMP-VH96-78RM is a high-severity cross-site request forgery (CSRF) vulnerability in zendframework/zend-feed (composer), affecting versions >= 1.0.0, < 2.10.3. It is fixed in 2.10.3. A victim's authenticated browser session is used to submit forged requests to an application that cannot distinguish them from legitimate ones.
2. How severe is GHSA-JMMP-VH96-78RM? GHSA-JMMP-VH96-78RM 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/zend-feed are affected by GHSA-JMMP-VH96-78RM? zendframework/zend-feed (composer) versions >= 1.0.0, < 2.10.3 is affected.
4. Is there a fix for GHSA-JMMP-VH96-78RM? Yes. GHSA-JMMP-VH96-78RM is fixed in 2.10.3. Upgrade to this version or later.
5. Is GHSA-JMMP-VH96-78RM exploitable, and should I be worried? Whether GHSA-JMMP-VH96-78RM 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-JMMP-VH96-78RM 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-JMMP-VH96-78RM? Upgrade zendframework/zend-feed to 2.10.3 or later.

Other vulnerabilities in zendframework/zend-feed