How severe is GHSA-4c2w-v5rq-5mx7?

No CVSS score has been assigned to GHSA-4c2w-v5rq-5mx7 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-4c2w-v5rq-5mx7?

GHSA-4c2w-v5rq-5mx7 affects the following packages: ezsystems/ezplatform-admin-ui-assets (Packagist), ezsystems/ezplatform-admin-ui-assets (Packagist), ezsystems/ezplatform-admin-ui-assets (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-4c2w-v5rq-5mx7?

Update ezsystems/ezplatform-admin-ui-assets to 4.2.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4c2w-v5rq-5mx7 is resolved across your whole dependency graph.

How do I detect GHSA-4c2w-v5rq-5mx7 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ezsystems/ezplatform-admin-ui-assets. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-4c2w-v5rq-5mx7 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-4c2w-v5rq-5mx7?

O3 pinpoints whether GHSA-4c2w-v5rq-5mx7 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-4c2w-v5rq-5mx7 actively exploited in the wild?

No public exploit code has been indexed for GHSA-4c2w-v5rq-5mx7 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-4c2w-v5rq-5mx7 published, and has it been updated?

GHSA-4c2w-v5rq-5mx7 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

GHSA-4c2w-v5rq-5mx7

eZ Platform Editor Cross-site Scripting (XSS)

Published

May 15, 2024

Updated

Nov 29, 2024

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Blast Radius

3 pkgs affected

🐘ezsystems/ezplatform-admin-ui-assets🐘ezsystems/ezplatform-admin-ui-assets🐘ezsystems/ezplatform-admin-ui-assets

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 two issues of low to medium severity. We recommend that you install the update as soon as possible.

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

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`ezsystems/ezplatform-admin-ui-assets`	≥ 4.2.0&&< 4.2.1	4.2.1
🐘Packagist	`ezsystems/ezplatform-admin-ui-assets`	≥ 5.0.0&&< 5.0.1	5.0.1
🐘Packagist	`ezsystems/ezplatform-admin-ui-assets`	≥ 5.1.0&&< 5.1.1	5.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-admin-ui-assets. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update ezsystems/ezplatform-admin-ui-assets to 4.2.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4c2w-v5rq-5mx7 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 pinpoints whether GHSA-4c2w-v5rq-5mx7 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-4c2w-v5rq-5mx7. 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 two issues of low to medium severity. We recommend that you install the update as soon as possible. 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/Plat

O3 Security · Impact-Aware SCA

Is GHSA-4c2w-v5rq-5mx7 in your dependencies?

O3 detects GHSA-4c2w-v5rq-5mx7 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works