How severe is GHSA-w9p3-26fx-5mp3?

No CVSS score has been assigned to GHSA-w9p3-26fx-5mp3 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-w9p3-26fx-5mp3?

GHSA-w9p3-26fx-5mp3 affects the following packages: ezsystems/platform-ui-assets-bundle (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-w9p3-26fx-5mp3?

Update ezsystems/platform-ui-assets-bundle to 4.2.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w9p3-26fx-5mp3 is resolved across your whole dependency graph.

How do I detect GHSA-w9p3-26fx-5mp3 in my Packagist dependencies?

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

How do I mitigate GHSA-w9p3-26fx-5mp3 if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is GHSA-w9p3-26fx-5mp3 actively exploited in the wild?

No public exploit code has been indexed for GHSA-w9p3-26fx-5mp3 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-w9p3-26fx-5mp3 published, and has it been updated?

GHSA-w9p3-26fx-5mp3 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-w9p3-26fx-5mp3 — ezsystems/platform-ui-ass…

GHSA-w9p3-26fx-5mp3 is a security vulnerability in ezsystems/platform-ui-assets-bundle. A fix is available for ezsystems/platform-ui-assets-bundle — see the affected versions and patch details below.

eZ Platform Admin UI is vulnerable to Cross-site Scripting (XSS)

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/platform-ui-assets-bundle

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

eZ Platform v1.13.x: ezsystems/PlatformUIAssetsBundle v4.2.3 (included from ezsystems/PlatformUIBundle v1.13.x)

eZ Platform v2.5.13: ezsystems/ezplatform-admin-ui-assets v4.2.1

eZ Platform v3.0.*: ezsystems/ezplatform-admin-ui-assets v5.0.1

eZ Platform v3.1.2: ezsystems/ezplatform-admin-ui-assets v5.1.1

Drafts that are sent to trash become visible in the Review Queue, even for users that were not able to see them before this action. It's not possible to preview them, but their title and review history is displayed. This affects Enterprise Edition only, of which ezplatform-workflow is a part. This security update is distributed via Composer, for

eZ Platform EE v2.5.13: ezsystems/ezplatform-workflow v1.1.9

eZ Platform EE v3.1.2: ezsystems/ezplatform-workflow v2.1.1

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`ezsystems/platform-ui-assets-bundle`	≥ 4.2.0&&< 4.2.3	4.2.3`composer require ezsystems/platform-ui-assets-bundle:^4.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/platform-ui-assets-bundle, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update ezsystems/platform-ui-assets-bundle to 4.2.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w9p3-26fx-5mp3 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

There is an XSS vulnerability in CKEditor, which is used by AlloyEditor, which is used in eZ Platform Admin UI. Scripts can be injected through specially crafted "protected" comments. We are not sure it is exploitable in eZ Platform, but recommend installing it to be on the safe side. It is fixed in CKEditor v4.14, AlloyEditor v2.11.9. It is distributed via Composer, for: ``` eZ Platform v1.13.x: ezsystems/PlatformUIAssetsBundle v4.2.3 (included from ezsystems/PlatformUIBundle v1.13.x) eZ Platform v2.5.13: ezsystems/ezplatform-admin-ui-assets v4.2.1 eZ Platform v3.0.*: ezsystems/ezplatform-a

O3 Security · Impact-Aware SCA

Is GHSA-w9p3-26fx-5mp3 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works