Summary
Ez Platform Object Injection in legacy shop module
This Security Advisory is about a vulnerability in the Legacy shop module. A backend editor could perform object injection in discount rules. This would require backend access and permission to edit discount rules. While object injection in itself is a serious vulnerability, the permission requirement means that normally only administrators would be able to exploit it, that's why it was classified as Medium severity.
Impact
Untrusted input is evaluated as executable code within the application's runtime environment. Typical impact: arbitrary code execution within the application's privilege context.
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
ezsystems/ezpublish-legacy to 2019.3.5.1 or later; ezsystems/ezpublish-legacy to 2017.12.7.3 or later; ezsystems/ezpublish-legacy to 5.4.14.2 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is GHSA-39J2-4P9J-5W4J? GHSA-39J2-4P9J-5W4J is a medium-severity code injection vulnerability in ezsystems/ezpublish-legacy (composer), affecting versions >= 2019.3.0, < 2019.3.5.1. It is fixed in 2019.3.5.1, 2017.12.7.3, 5.4.14.2. Untrusted input is evaluated as executable code within the application's runtime environment.
- Which versions of ezsystems/ezpublish-legacy are affected by GHSA-39J2-4P9J-5W4J? ezsystems/ezpublish-legacy (composer) versions >= 2019.3.0, < 2019.3.5.1 is affected.
- Is there a fix for GHSA-39J2-4P9J-5W4J? Yes. GHSA-39J2-4P9J-5W4J is fixed in 2019.3.5.1, 2017.12.7.3, 5.4.14.2. Upgrade to this version or later.
- Is GHSA-39J2-4P9J-5W4J exploitable, and should I be worried? Whether GHSA-39J2-4P9J-5W4J 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-39J2-4P9J-5W4J 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-39J2-4P9J-5W4J?
- Upgrade
ezsystems/ezpublish-legacyto 2019.3.5.1 or later - Upgrade
ezsystems/ezpublish-legacyto 2017.12.7.3 or later - Upgrade
ezsystems/ezpublish-legacyto 5.4.14.2 or later
- Upgrade