How severe is GHSA-7vwg-39h8-8qp8?

No CVSS score has been assigned to GHSA-7vwg-39h8-8qp8 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-7vwg-39h8-8qp8?

GHSA-7vwg-39h8-8qp8 affects the following packages: ezsystems/ezplatform-rest (Packagist), ezsystems/ezplatform-rest (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-7vwg-39h8-8qp8?

Update ezsystems/ezplatform-rest to 1.2.2.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7vwg-39h8-8qp8 is resolved across your whole dependency graph.

How do I detect GHSA-7vwg-39h8-8qp8 in my Packagist dependencies?

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

How do I mitigate GHSA-7vwg-39h8-8qp8 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-7vwg-39h8-8qp8 actively exploited in the wild?

No public exploit code has been indexed for GHSA-7vwg-39h8-8qp8 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-7vwg-39h8-8qp8 published, and has it been updated?

GHSA-7vwg-39h8-8qp8 was published on March 11, 2021 and was last updated on December 2, 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-7vwg-39h8-8qp8: ezplatform-rest

Real-World Exposure

2 pkgs affected

🐘ezsystems/ezplatform-rest🐘ezsystems/ezplatform-rest

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 eZ Platform v1.13, v2.5, and v3.2, and in Ibexa DXP and Ibexa Open Source v3.3. The /user/sessions endpoint can let an attacker detect if a given username or email refers to a valid account. This can be detected through differences in the response data or response time of certain requests. The fix ensures neither attack is possible. The fix is distributed via Composer.

If you come across a security issue in our products, here is how you can report it to us: https://doc.ibexa.co/en/latest/guide/reporting_issues/#toc

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`ezsystems/ezplatform-rest`	≥ 1.2.0&&< 1.2.2.1	1.2.2.1`composer require ezsystems/ezplatform-rest:^1.2.2.1`
🐘Packagist	`ezsystems/ezplatform-rest`	≥ 1.3.0&&< 1.3.1.1	1.3.1.1`composer require ezsystems/ezplatform-rest:^1.3.1.1`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ezsystems/ezplatform-rest, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update ezsystems/ezplatform-rest to 1.2.2.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7vwg-39h8-8qp8 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 eZ Platform v1.13, v2.5, and v3.2, and in Ibexa DXP and Ibexa Open Source v3.3. The /user/sessions endpoint can let an attacker detect if a given username or email refers to a valid account. This can be detected through differences in the response data or response time of certain requests. The fix ensures neither attack is possible. The fix is distributed via Composer. If you come across a security issue in our products, here is how you can report it to us: https://doc.ibexa.co/en/latest/guide/reporting_issues/#toc

O3 Security · Impact-Aware SCA

Is GHSA-7vwg-39h8-8qp8 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works