How severe is GHSA-xmp3-7745-g4vj?

No CVSS score has been assigned to GHSA-xmp3-7745-g4vj yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-xmp3-7745-g4vj?

GHSA-xmp3-7745-g4vj affects the following packages: ezsystems/ez-support-tools (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-xmp3-7745-g4vj?

Update ezsystems/ez-support-tools to 2.2.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xmp3-7745-g4vj is resolved across your whole dependency graph.

How do I detect GHSA-xmp3-7745-g4vj in my Packagist dependencies?

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

How do I mitigate GHSA-xmp3-7745-g4vj 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-xmp3-7745-g4vj actively exploited in the wild?

No public exploit code has been indexed for GHSA-xmp3-7745-g4vj 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-xmp3-7745-g4vj published, and has it been updated?

GHSA-xmp3-7745-g4vj 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.

ezsystems/ez-support-tools Failing access control in…

Real-World Exposure

1 pkg affected

🐘ezsystems/ez-support-tools

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 is about a vulnerability in ezsystems/ez-support-tools v2.2, part of Ibexa DXP v3.2. Older versions are not affected. A user having insufficient permissions is able to access the system information tabs if they type in the direct link (the link is not shown in the menu). The "Setup / System info" policy should be required to access it, but only backend login is actually required. This means any editor can see core system information, including the output from phpinfo(). The fix ensures that the access policy is correctly verified.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`ezsystems/ez-support-tools`	≥ 2.2.0&&< 2.2.3	2.2.3`composer require ezsystems/ez-support-tools:^2.2.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/ez-support-tools, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update ezsystems/ez-support-tools to 2.2.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xmp3-7745-g4vj 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 is about a vulnerability in ezsystems/ez-support-tools v2.2, part of Ibexa DXP v3.2. Older versions are not affected. A user having insufficient permissions is able to access the system information tabs if they type in the direct link (the link is not shown in the menu). The "Setup / System info" policy should be required to access it, but only backend login is actually required. This means any editor can see core system information, including the output from phpinfo(). The fix ensures that the access policy is correctly verified.

O3 Security · Impact-Aware SCA

Is GHSA-xmp3-7745-g4vj in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works

ezsystems/ez-support-tools Failing access control in system info viewGHSA-xmp3-7745-g4vj