Summary
Content object state fetch functions open to SQL injection
Impact
This Security Update is about a vulnerability in eZ Publish Legacy. The content object state code could be vulnerable to SQL injection. There is no known exploit, but one might be possible. If you use Legacy in any way, we strongly recommend that you install this update as soon as possible.
Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access. Typical impact: data disclosure or modification.
Affected versions
Security releases
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
The fix is distributed via Composer, see "Patched versions".
Frequently Asked Questions
- What is GHSA-JPWX-FFJQ-WR4W? GHSA-JPWX-FFJQ-WR4W is a high-severity SQL injection vulnerability in ezsystems/ezpublish-legacy (composer), affecting versions >= 2018.06.0, <= 2019.03.5.1. It is fixed in 2019.03.6.1, 2017.12.7.4. Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access.
- Which versions of ezsystems/ezpublish-legacy are affected by GHSA-JPWX-FFJQ-WR4W? ezsystems/ezpublish-legacy (composer) versions >= 2018.06.0, <= 2019.03.5.1 is affected.
- Is there a fix for GHSA-JPWX-FFJQ-WR4W? Yes. GHSA-JPWX-FFJQ-WR4W is fixed in 2019.03.6.1, 2017.12.7.4. Upgrade to this version or later.
- Is GHSA-JPWX-FFJQ-WR4W exploitable, and should I be worried? Whether GHSA-JPWX-FFJQ-WR4W 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
- What actually determines whether GHSA-JPWX-FFJQ-WR4W 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.
- How do I fix GHSA-JPWX-FFJQ-WR4W?
- Upgrade
ezsystems/ezpublish-legacyto 2019.03.6.1 or later - Upgrade
ezsystems/ezpublish-legacyto 2017.12.7.4 or later
- Upgrade