Skip to content
Fencer Intel
medium —

GHSA-w9p3-26fx-5mp3 json

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

published 2y ago modified last yr.

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

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

Patch / fix

  • packagist ezsystems/platform-ui-assets-bundle 4.2.3

Is GHSA-w9p3-26fx-5mp3 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem package affected fixed in
packagist ezsystems/platform-ui-assets-bundle
>=4.2.0, <4.2.3
4.2.3

Classification

Weakness
  • CWE-79 Improper Neutralization of Input During Web Page Generation

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.