Skip to content
Fencer Vulns
medium 5.4

CVE-2022-30429 json

Neos CMS vulnerable to XSS in various backend modules

published 2022-06-02 4 y ago modified 2026-06-17 4 mo ago also BIT-neos-2022-30429 , EUVD-2022-5982 , GHSA-7m9h-v68w-pfw3

cvss
5.4
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.6%
EPSS 0.6% chance of exploitation in 30 days, percentile 49%
public exploits
0
none known

Summary

Multiple cross-site scripting (XSS) vulnerabilities in Neos CMS allow attackers with the editor role or higher to inject arbitrary script or HTML code using the editor function, the deletion of assets, or a workspace title. The vulnerabilities were found in versions 3.3.29 and 8.0.1 and could also be present in all intermediate versions.

Patch / fix

  • packagist neos/neos 4.4.0, 5.3.10, 7.0.9, 7.1.7, 7.2.6, 7.3.4, 8.0.2
  • bitnami neos 5.3.10, 7.0.9, 7.1.7, 7.2.6, 7.3.4, 8.0.2
  • neos neos_cms 5.3.10, 7.0.9, 7.1.7, 7.2.6, 7.3.4, 8.0.2

Exploit prediction

0.60% chance of exploitation in the next 30 days, higher than 49% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • it-sec.de https://it-sec.de/unbekannte-schwachstellen-in-neos-cms/ referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
GitHub 3.1 5.4 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
NVD 3.1 5.4 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
NVD 2.0 3.5 AV:N/AC:M/Au:S/C:N/I:P/A:N
OSV 3.1 5.4 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

Affected packages

ecosystem package affected fixed in
packagist neos/neos
>=3.3.0, <4.4.0
>=5.3.0, <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
4.4.0
5.3.10
7.0.9
7.1.7
7.2.6
7.3.4
8.0.2
bitnami neos
>=3.3.0, <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

Fencer Vulns 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.