Summary
eZ Publish Legacy Passwordless login for LDAP users
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.
Installations that are using the legacy LDAP login handler or the TextFile login handler in combination with the standard legacy login handler, may in rare cases be vulnerable to a failure of the standard login handler to verify passwords correctly, allowing unauthorised access.
If your installation has never used the LDAP or TextFile login handlers, or never used legacy login at all, then it is not affected. Still, we recommend installing the update, to be on the safe side.
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/13f03a2be6c0ee4d0caaafaef05904ea9b0c4d9d
Impact
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 2018.9.1.1 or later; ezsystems/ezpublish-legacy to 2018.6.1.2 or later; ezsystems/ezpublish-legacy to 2017.12.4.1 or later; ezsystems/ezpublish-legacy to 5.4.12.1 or later; ezsystems/ezpublish-legacy to 5.3.12.4 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is GHSA-P9MP-VQ4V-V5M5? GHSA-P9MP-VQ4V-V5M5 is a high-severity security vulnerability in ezsystems/ezpublish-legacy (composer), affecting versions >= 2018.9.0, < 2018.9.1.1. It is fixed in 2018.9.1.1, 2018.6.1.2, 2017.12.4.1, 5.4.12.1, 5.3.12.4.
- Which versions of ezsystems/ezpublish-legacy are affected by GHSA-P9MP-VQ4V-V5M5? ezsystems/ezpublish-legacy (composer) versions >= 2018.9.0, < 2018.9.1.1 is affected.
- Is there a fix for GHSA-P9MP-VQ4V-V5M5? Yes. GHSA-P9MP-VQ4V-V5M5 is fixed in 2018.9.1.1, 2018.6.1.2, 2017.12.4.1, 5.4.12.1, 5.3.12.4. Upgrade to this version or later.
- Is GHSA-P9MP-VQ4V-V5M5 exploitable, and should I be worried? Whether GHSA-P9MP-VQ4V-V5M5 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-P9MP-VQ4V-V5M5 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-P9MP-VQ4V-V5M5?
- Upgrade
ezsystems/ezpublish-legacyto 2018.9.1.1 or later - Upgrade
ezsystems/ezpublish-legacyto 2018.6.1.2 or later - Upgrade
ezsystems/ezpublish-legacyto 2017.12.4.1 or later - Upgrade
ezsystems/ezpublish-legacyto 5.4.12.1 or later - Upgrade
ezsystems/ezpublish-legacyto 5.3.12.4 or later
- Upgrade