GHSA-2VH3-CJ9J-MCJ5

GHSA-2VH3-CJ9J-MCJ5 is a medium-severity cross-site scripting (XSS) vulnerability in ezsystems/ezpublish-legacy (composer), affecting versions >= 2018.9.0, < 2018.9.1.2. It is fixed in 2018.9.1.2, 2018.6.1.3, 2017.12.4.2, 5.4.12.2, 5.3.12.5.

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

eZ Publish Legacy Cross-site Scripting (XSS) in 'disabled module' error template

This security advisory fixes a vulnerability in eZ Publish Legacy, and we recommend that you install it as soon as possible if you are using Legacy via the LegacyBridge.

Installations where all modules are disabled may be vulnerable to XSS injection in the module name. This is a rare configuration, but we still recommend installing the update, which adds the necessary input washing.

To install, use Composer to update to one of the "Resolving versions" mentioned above, or apply this patch manually:
https://github.com/ezsystems/ezpublish-legacy/commit/4697bff700e8cf95d5847ea19dad3479a77b02d9

Impact

Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.

Affected versions

ezsystems/ezpublish-legacy (>= 2018.9.0, < 2018.9.1.2) ezsystems/ezpublish-legacy (>= 2018.6.0, < 2018.6.1.3) ezsystems/ezpublish-legacy (>= 2011.0.0, < 2017.12.4.2) ezsystems/ezpublish-legacy (>= 5.4.0, < 5.4.12.2) ezsystems/ezpublish-legacy (>= 5.3.0, < 5.3.12.5)

Security releases

ezsystems/ezpublish-legacy → 2018.9.1.2 (composer) ezsystems/ezpublish-legacy → 2018.6.1.3 (composer) ezsystems/ezpublish-legacy → 2017.12.4.2 (composer) ezsystems/ezpublish-legacy → 5.4.12.2 (composer) ezsystems/ezpublish-legacy → 5.3.12.5 (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:

ezsystems/ezpublish-legacy to 2018.9.1.2 or later; ezsystems/ezpublish-legacy to 2018.6.1.3 or later; ezsystems/ezpublish-legacy to 2017.12.4.2 or later; ezsystems/ezpublish-legacy to 5.4.12.2 or later; ezsystems/ezpublish-legacy to 5.3.12.5 or later

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

Frequently Asked Questions

  1. What is GHSA-2VH3-CJ9J-MCJ5? GHSA-2VH3-CJ9J-MCJ5 is a medium-severity cross-site scripting (XSS) vulnerability in ezsystems/ezpublish-legacy (composer), affecting versions >= 2018.9.0, < 2018.9.1.2. It is fixed in 2018.9.1.2, 2018.6.1.3, 2017.12.4.2, 5.4.12.2, 5.3.12.5. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
  2. Which versions of ezsystems/ezpublish-legacy are affected by GHSA-2VH3-CJ9J-MCJ5? ezsystems/ezpublish-legacy (composer) versions >= 2018.9.0, < 2018.9.1.2 is affected.
  3. Is there a fix for GHSA-2VH3-CJ9J-MCJ5? Yes. GHSA-2VH3-CJ9J-MCJ5 is fixed in 2018.9.1.2, 2018.6.1.3, 2017.12.4.2, 5.4.12.2, 5.3.12.5. Upgrade to this version or later.
  4. Is GHSA-2VH3-CJ9J-MCJ5 exploitable, and should I be worried? Whether GHSA-2VH3-CJ9J-MCJ5 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
  5. What actually determines whether GHSA-2VH3-CJ9J-MCJ5 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.
  6. How do I fix GHSA-2VH3-CJ9J-MCJ5?
    • Upgrade ezsystems/ezpublish-legacy to 2018.9.1.2 or later
    • Upgrade ezsystems/ezpublish-legacy to 2018.6.1.3 or later
    • Upgrade ezsystems/ezpublish-legacy to 2017.12.4.2 or later
    • Upgrade ezsystems/ezpublish-legacy to 5.4.12.2 or later
    • Upgrade ezsystems/ezpublish-legacy to 5.3.12.5 or later

Other vulnerabilities in ezsystems/ezpublish-legacy

Stop the waste.
Protect your environment with Kodem.