How severe is GHSA-82rv-45pc-v28w?

No CVSS score has been assigned to GHSA-82rv-45pc-v28w yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-82rv-45pc-v28w?

GHSA-82rv-45pc-v28w affects the following packages: ezsystems/ezpublish-legacy (Packagist), ezsystems/ezpublish-legacy (Packagist), ezsystems/ezpublish-legacy (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-82rv-45pc-v28w?

Update ezsystems/ezpublish-legacy to 2017.12.2.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-82rv-45pc-v28w is resolved across your whole dependency graph.

How do I detect GHSA-82rv-45pc-v28w in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ezsystems/ezpublish-legacy. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-82rv-45pc-v28w 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.

How does O3 Security protect against GHSA-82rv-45pc-v28w?

O3 pinpoints whether GHSA-82rv-45pc-v28w is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-82rv-45pc-v28w actively exploited in the wild?

No public exploit code has been indexed for GHSA-82rv-45pc-v28w 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-82rv-45pc-v28w published, and has it been updated?

GHSA-82rv-45pc-v28w 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

GHSA-82rv-45pc-v28w

eZ Publish Legacy Patch EZSA-2018-001 for Several vulnerabilities

Published

May 15, 2024

Updated

Nov 29, 2024

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Blast Radius

3 pkgs affected

🐘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 4 separate vulnerabilities in eZ Publish Legacy, and we recommend that you install it as soon as possible if you are using Legacy by itself or via the LegacyBridge.

First, it increases the randomness, and thus the security, of the pseudo-random bytes used to generate a hash for the "forgot password" feature. This protects accounts against being taken over through attacks trying to predict the hash. If the increased randomness is not available in your PHP installation, it will now log a warning.

Second, it improves security of the information collector feature, by ensuring no collection emails will be sent from invalid manipulated forms.

Third, it stops the possible leaking of the names of content objects that should not be readable for certain users, on installations where these users can create or edit XML text.

Fourth, it protects against cross-site scripting (XSS) in the Matrix data type, on installations where users are allowed to edit content classes / content types.

We recommend that you install the security update as soon as possible.

To install, use Composer to update to one of the "Resolving versions" mentioned above, or apply these patches manually: https://github.com/ezsystems/ezpublish-legacy/commit/917711eb7ffe2b52a3e9fe12505f6810a63696f7 https://github.com/ezsystems/ezpublish-legacy/commit/6db0e6b7739481f27d954548388bd3f0ed2c6fdd https://github.com/ezsystems/ezpublish-legacy/commit/efcd2b61b15eaaf74e0ff28d6c723cf28e655dab https://github.com/ezsystems/ezpublish-legacy/commit/f9ffaf590b63b4f552142cfd4441afbbfb3f19b1

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`ezsystems/ezpublish-legacy`	≥ 2011.0.0&&< 2017.12.2.1	2017.12.2.1
🐘Packagist	`ezsystems/ezpublish-legacy`	≥ 5.4.0&&< 5.4.11.3	5.4.11.3
🐘Packagist	`ezsystems/ezpublish-legacy`	≥ 5.3.0&&< 5.3.12.3	5.3.12.3

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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update ezsystems/ezpublish-legacy to 2017.12.2.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-82rv-45pc-v28w 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.
How O3 protects you
O3 pinpoints whether GHSA-82rv-45pc-v28w is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-82rv-45pc-v28w. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

This security advisory fixes 4 separate vulnerabilities in eZ Publish Legacy, and we recommend that you install it as soon as possible if you are using Legacy by itself or via the LegacyBridge. First, it increases the randomness, and thus the security, of the pseudo-random bytes used to generate a hash for the "forgot password" feature. This protects accounts against being taken over through attacks trying to predict the hash. If the increased randomness is not available in your PHP installation, it will now log a warning. Second, it improves security of the information collector feature,

O3 Security · Impact-Aware SCA

Is GHSA-82rv-45pc-v28w in your dependencies?

O3 detects GHSA-82rv-45pc-v28w across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works