GHSA-4c2w-v5rq-5mx7 — ezsystems/ezplatform-admi…
GHSA-4c2w-v5rq-5mx7 is a security vulnerability in ezsystems/ezplatform-admin-ui-assets. A fix is available for ezsystems/ezplatform-admin-ui-assets — see the affected versions and patch details below.
eZ Platform Editor Cross-site Scripting (XSS)
Real-World Exposure
ezsystems/ezplatform-admin-ui-assets🐘ezsystems/ezplatform-admin-ui-assets🐘ezsystems/ezplatform-admin-ui-assetsReal-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
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | ezsystems/ezplatform-admin-ui-assets | ≥ 4.2.0&&< 4.2.1 | 4.2.1composer require ezsystems/ezplatform-admin-ui-assets:^4.2.1 |
| 🐘Packagist | ezsystems/ezplatform-admin-ui-assets | ≥ 5.0.0&&< 5.0.1 | 5.0.1composer require ezsystems/ezplatform-admin-ui-assets:^5.0.1 |
| 🐘Packagist | ezsystems/ezplatform-admin-ui-assets | ≥ 5.1.0&&< 5.1.1 | 5.1.1composer require ezsystems/ezplatform-admin-ui-assets:^5.1.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ezsystems/ezplatform-admin-ui-assets, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-4c2w-v5rq-5mx7 can be triaged on real exposure rather than presence alone.
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
Is GHSA-4c2w-v5rq-5mx7 in your dependencies?
O3 Security finds GHSA-4c2w-v5rq-5mx7 across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.