How severe is GHSA-cc2j-92jq-wgjg?

No CVSS score has been assigned to GHSA-cc2j-92jq-wgjg yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-cc2j-92jq-wgjg?

GHSA-cc2j-92jq-wgjg affects the following packages: ezsystems/ezpublish-legacy (Packagist), ezsystems/ezpublish-legacy (Packagist), ezsystems/ezpublish-legacy (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-cc2j-92jq-wgjg?

Update ezsystems/ezpublish-legacy to 2017.8.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cc2j-92jq-wgjg is resolved across your whole dependency graph.

How do I detect GHSA-cc2j-92jq-wgjg 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-cc2j-92jq-wgjg 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-cc2j-92jq-wgjg?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-cc2j-92jq-wgjg can be triaged on real exposure rather than presence alone.

Is GHSA-cc2j-92jq-wgjg actively exploited in the wild?

No public exploit code has been indexed for GHSA-cc2j-92jq-wgjg 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-cc2j-92jq-wgjg published, and has it been updated?

GHSA-cc2j-92jq-wgjg 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.

GHSA-cc2j-92jq-wgjg: ezsystems/ezpublish

Real-World Exposure

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 an information disclosure vulnerability in the legacy admin content tree menu. If a view has been disabled in site.ini [SiteAccessRules] Rules, and an attacker accesses the backend with the URL to this module, then the tree menu may be displayed. Since the tree menu may contain hidden items, this may lead to information disclosure. We recommend that you install this Security Update as soon as possible.

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

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`ezsystems/ezpublish-legacy`	≥ 2011.0.0&&< 2017.8.1.1	2017.8.1.1`composer require ezsystems/ezpublish-legacy:^2017.8.1.1`
🐘Packagist	`ezsystems/ezpublish-legacy`	≥ 5.4.0&&< 5.4.10.1	5.4.10.1`composer require ezsystems/ezpublish-legacy:^5.4.10.1`
🐘Packagist	`ezsystems/ezpublish-legacy`	≥ 5.3.0&&< 5.3.12.2	5.3.12.2`composer require ezsystems/ezpublish-legacy:^5.3.12.2`

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 2017.8.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cc2j-92jq-wgjg 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-cc2j-92jq-wgjg can be triaged on real exposure rather than presence alone.

Tailored to GHSA-cc2j-92jq-wgjg. 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 an information disclosure vulnerability in the legacy admin content tree menu. If a view has been disabled in site.ini [SiteAccessRules] Rules, and an attacker accesses the backend with the URL to this module, then the tree menu may be displayed. Since the tree menu may contain hidden items, this may lead to information disclosure. We recommend that you install this Security Update as soon as possible. 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/c

O3 Security · Impact-Aware SCA

Is GHSA-cc2j-92jq-wgjg in your dependencies?

O3 Security finds GHSA-cc2j-92jq-wgjg across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works

GHSA-cc2j-92jq-wgjg — ezsystems/ezpublish-legacy

Real-World Exposure

Description

Affected Packages

Detection & mitigation playbook

Detect

Fix

Workarounds

How O3 protects you

Frequently Asked Questions

Is GHSA-cc2j-92jq-wgjg in your dependencies?