How severe is GHSA-2vh3-cj9j-mcj5?

No CVSS score has been assigned to GHSA-2vh3-cj9j-mcj5 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-2vh3-cj9j-mcj5?

GHSA-2vh3-cj9j-mcj5 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-2vh3-cj9j-mcj5?

Update ezsystems/ezpublish-legacy to 2018.9.1.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2vh3-cj9j-mcj5 is resolved across your whole dependency graph.

How do I detect GHSA-2vh3-cj9j-mcj5 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-2vh3-cj9j-mcj5 if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is GHSA-2vh3-cj9j-mcj5 actively exploited in the wild?

No public exploit code has been indexed for GHSA-2vh3-cj9j-mcj5 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-2vh3-cj9j-mcj5 published, and has it been updated?

GHSA-2vh3-cj9j-mcj5 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 Cross-site Scripting (XSS) in 'disabled module' error templateGHSA-2vh3-cj9j-mcj5

Fix: ezsystems/ezpublish-legacy@4697bff

GHSA-2vh3-cj9j-mcj5 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 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

Affected Packages

5 total 5 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`ezsystems/ezpublish-legacy`	≥ 2018.9.0&&< 2018.9.1.2	2018.9.1.2`composer require ezsystems/ezpublish-legacy:^2018.9.1.2`
🐘Packagist	`ezsystems/ezpublish-legacy`	≥ 2018.6.0&&< 2018.6.1.3	2018.6.1.3`composer require ezsystems/ezpublish-legacy:^2018.6.1.3`
🐘Packagist	`ezsystems/ezpublish-legacy`	≥ 2011.0.0&&< 2017.12.4.2	2017.12.4.2`composer require ezsystems/ezpublish-legacy:^2017.12.4.2`
🐘Packagist	`ezsystems/ezpublish-legacy`	≥ 5.4.0&&< 5.4.12.2	5.4.12.2`composer require ezsystems/ezpublish-legacy:^5.4.12.2`
🐘Packagist	`ezsystems/ezpublish-legacy`	≥ 5.3.0&&< 5.3.12.5	5.3.12.5`composer require ezsystems/ezpublish-legacy:^5.3.12.5`

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.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2vh3-cj9j-mcj5 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

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 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

O3 Security · Impact-Aware SCA

Is GHSA-2vh3-cj9j-mcj5 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works