How severe is GHSA-2w9p-xxqr-h253?

No CVSS score has been assigned to GHSA-2w9p-xxqr-h253 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-2w9p-xxqr-h253?

GHSA-2w9p-xxqr-h253 affects the following packages: ezsystems/ezplatform-kernel (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-2w9p-xxqr-h253?

Update ezsystems/ezplatform-kernel to 1.0.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2w9p-xxqr-h253 is resolved across your whole dependency graph.

How do I detect GHSA-2w9p-xxqr-h253 in my Packagist dependencies?

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

How do I mitigate GHSA-2w9p-xxqr-h253 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-2w9p-xxqr-h253?

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

Is GHSA-2w9p-xxqr-h253 actively exploited in the wild?

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

GHSA-2w9p-xxqr-h253 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

GHSA-2w9p-xxqr-h253 — ezsystems/ezplatform-kern…

GHSA-2w9p-xxqr-h253 is a remote code execution vulnerability in ezsystems/ezplatform-kernel. A fix is available for ezsystems/ezplatform-kernel — see the affected versions and patch details below.

eZ Platform Object Injection in SiteAccessMatchListener

Published

May 15, 2024

Updated

Nov 29, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 29, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐘ezsystems/ezplatform-kernel

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

Update: There are bugs introduced by this fix, particularly but not limited to compound siteaccess matchers. These have been fixed in ezsystems/ezplatform-kernel v1.0.3, and in ezsystems/ezpublish-kernel v7.5.8, v6.13.6.4, and v5.4.15.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`ezsystems/ezplatform-kernel`	≥ 1.0.0&&< 1.0.3	1.0.3`composer require ezsystems/ezplatform-kernel:^1.0.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/ezplatform-kernel, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update ezsystems/ezplatform-kernel to 1.0.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2w9p-xxqr-h253 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-2w9p-xxqr-h253 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-2w9p-xxqr-h253. 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 is about an object injection vulnerability in the SiteAccessMatchListener of eZ Platform, which could lead to remote code execution (RCE), a very serious threat. All sites may be affected. Update: There are bugs introduced by this fix, particularly but not limited to compound siteaccess matchers. These have been fixed in ezsystems/ezplatform-kernel v1.0.3, and in ezsystems/ezpublish-kernel v7.5.8, v6.13.6.4, and v5.4.15.

O3 Security · Impact-Aware SCA

Is GHSA-2w9p-xxqr-h253 in your dependencies?

O3 Security finds GHSA-2w9p-xxqr-h253 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