# GHSA-4c2w-v5rq-5mx7: eZ Platform Editor Cross-site Scripting (XSS) > Attackers can inject scripts via crafted comments or view unauthorized draft titles in the review queue, requiring updates to CKEditor and workflow modules. - **Severity:** Not scored - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 15 May 2024 ## What is GHSA-4c2w-v5rq-5mx7? GHSA-4c2w-v5rq-5mx7 is a cross-site scripting vulnerability in ezsystems/ezplatform-admin-ui-assets, published on 15 May 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link. ### Official 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 ## Which versions are affected by GHSA-4c2w-v5rq-5mx7? 6 open source packages ship an affected version, including ezsystems/ezplatform-admin-ui-assets. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `ezsystems/ezplatform-admin-ui-assets` | Packagist | From 4.2.0 | 4.2.1 | | `ezsystems/ezplatform-admin-ui-assets` | Packagist | From 4.2.0 | 4.2.1 | | `ezsystems/ezplatform-admin-ui-assets` | Packagist | From 5.0.0 | 5.0.1 | | `ezsystems/ezplatform-admin-ui-assets` | Packagist | From 5.0.0 | 5.0.1 | | `ezsystems/ezplatform-admin-ui-assets` | Packagist | From 5.1.0 | 5.1.1 | | `ezsystems/ezplatform-admin-ui-assets` | Packagist | From 5.1.0 | 5.1.1 | ## How do I fix GHSA-4c2w-v5rq-5mx7? Upgrade ezsystems/ezplatform-admin-ui-assets to a fixed version for your release line: 4.2.1, 5.0.1 or 5.1.1. ## Is GHSA-4c2w-v5rq-5mx7 being exploited? There is no known exploitation of GHSA-4c2w-v5rq-5mx7 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for GHSA-4c2w-v5rq-5mx7 and fix it if it is affected. What it is: GHSA-4c2w-v5rq-5mx7 is a cross-site scripting vulnerability in ezsystems/ezplatform-admin-ui-assets, published on 15 May 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of GHSA-4c2w-v5rq-5mx7 in the wild and no public exploit code. Affected packages and fixed versions: - ezsystems/ezplatform-admin-ui-assets (Packagist): affected from 4.2.0; fixed in 4.2.1 - ezsystems/ezplatform-admin-ui-assets (Packagist): affected from 4.2.0; fixed in 4.2.1 - ezsystems/ezplatform-admin-ui-assets (Packagist): affected from 5.0.0; fixed in 5.0.1 - ezsystems/ezplatform-admin-ui-assets (Packagist): affected from 5.0.0; fixed in 5.0.1 - ezsystems/ezplatform-admin-ui-assets (Packagist): affected from 5.1.0; fixed in 5.1.1 - ezsystems/ezplatform-admin-ui-assets (Packagist): affected from 5.1.0; fixed in 5.1.1 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/GHSA-4c2w-v5rq-5mx7/ (Markdown: https://insights.sbomify.com/GHSA-4c2w-v5rq-5mx7/index.md) ``` ## Sources - OSV: https://osv.dev/vulnerability/GHSA-4c2w-v5rq-5mx7 --- From sbomify Insights: https://insights.sbomify.com/GHSA-4c2w-v5rq-5mx7/ Summaries are generated and may contain mistakes; the official description above is the record.