GHSA-jfxf-4frr-9j3q json
XSS in various backend modules due to (un)escaping in JS notification module
published 4y 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
The notification module displaying flash messages unscapes HTML coming from the server, resulting in XSS vulnerabilities with various names and labels of entities (eg. workspace title or media title). This however means you must be a logged in user with respective rights in the first place to leverage the attack vector.
Patch / fix
- packagist neos/neos 5.3.10, 7.0.9, 7.1.7, 7.2.6, 7.3.4, 8.0.2
Is GHSA-jfxf-4frr-9j3q 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 FencerAffected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | neos/neos | >=3.3, <5.3.10 >=7.0.0, <7.0.9 >=7.1.0, <7.1.7 >=7.2.0, <7.2.6 >=7.3.0, <7.3.4 >=8.0.0, <8.0.2 |
5.3.10 7.0.9 7.1.7 7.2.6 7.3.4 8.0.2 |
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
References
Sources
- GitHub Advisory GHSA-jfxf-4frr-9j3q
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.