How severe is GHSA-p9mp-vq4v-v5m5?

No CVSS score has been assigned to GHSA-p9mp-vq4v-v5m5 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-p9mp-vq4v-v5m5?

GHSA-p9mp-vq4v-v5m5 affects the following packages: ezsystems/ezpublish-legacy (Packagist), ezsystems/ezpublish-legacy (Packagist), ezsystems/ezpublish-legacy (Packagist), ezsystems/ezpublish-legacy (Packagist), ezsystems/ezpublish-legacy (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-p9mp-vq4v-v5m5?

Update ezsystems/ezpublish-legacy to 2018.9.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-p9mp-vq4v-v5m5 is resolved across your whole dependency graph.

How do I detect GHSA-p9mp-vq4v-v5m5 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ezsystems/ezpublish-legacy, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-p9mp-vq4v-v5m5 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-p9mp-vq4v-v5m5 actively exploited in the wild?

No public exploit code has been indexed for GHSA-p9mp-vq4v-v5m5 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-p9mp-vq4v-v5m5 published, and has it been updated?

GHSA-p9mp-vq4v-v5m5 was published on May 15, 2024 and was last updated on November 29, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

Not in CISA KEV

eZ Publish Legacy Passwordless login for LDAP usersGHSA-p9mp-vq4v-v5m5

Fix: ezsystems/ezpublish-legacy#1394

GHSA-p9mp-vq4v-v5m5 is a security vulnerability in ezsystems/ezpublish-legacy. A fix is available for ezsystems/ezpublish-legacy — see the affected versions and patch details below.

Published

May 15, 2024

Updated

Nov 29, 2024

Affected

5 pkgs

Patched

5 / 5

Exploits

None indexed

Exploitation data as of Nov 29, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

5 pkgs affected

🐘ezsystems/ezpublish-legacy🐘ezsystems/ezpublish-legacy🐘ezsystems/ezpublish-legacy🐘ezsystems/ezpublish-legacy🐘ezsystems/ezpublish-legacy

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

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

Affected Packages

5 total 5 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`ezsystems/ezpublish-legacy`	≥ 2018.9.0&&< 2018.9.1.1	2018.9.1.1`composer require ezsystems/ezpublish-legacy:^2018.9.1.1`
🐘Packagist	`ezsystems/ezpublish-legacy`	≥ 2018.6.0&&< 2018.6.1.2	2018.6.1.2`composer require ezsystems/ezpublish-legacy:^2018.6.1.2`
🐘Packagist	`ezsystems/ezpublish-legacy`	≥ 2011.0.0&&< 2017.12.4.1	2017.12.4.1`composer require ezsystems/ezpublish-legacy:^2017.12.4.1`
🐘Packagist	`ezsystems/ezpublish-legacy`	≥ 5.4.0&&< 5.4.12.1	5.4.12.1`composer require ezsystems/ezpublish-legacy:^5.4.12.1`
🐘Packagist	`ezsystems/ezpublish-legacy`	≥ 5.3.0&&< 5.3.12.4	5.3.12.4`composer require ezsystems/ezpublish-legacy:^5.3.12.4`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ezsystems/ezpublish-legacy, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update ezsystems/ezpublish-legacy to 2018.9.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-p9mp-vq4v-v5m5 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

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 u

O3 Security · Impact-Aware SCA

Is GHSA-p9mp-vq4v-v5m5 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works