# CVE-2022-30429: Neos CMS vulnerable to XSS in various backend modules > Attackers with editor roles can inject arbitrary scripts via editor functions, asset deletion, or workspace titles in Neos CMS. - **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N`) - **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:** 2 Jun 2022 - **Updated:** 3 Aug 2024 - **Also known as:** BIT-neos-2022-30429, GHSA-7m9h-v68w-pfw3 ## What is CVE-2022-30429? CVE-2022-30429 is a medium-severity cross-site scripting vulnerability in n/a, published on 2 Jun 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link. ### Official description 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. Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation) ## Which versions are affected by CVE-2022-30429? 15 open source packages ship an affected version, including neos/neos and neos. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `neos/neos` | Packagist | From 3.3.0 | 4.4.0 | | `neos/neos` | Packagist | From 3.3.0 | 4.4.0 | | `neos/neos` | Packagist | From 5.3.0 | 5.3.10 | | `neos/neos` | Packagist | From 5.3.0 | 5.3.10 | | `neos/neos` | Packagist | From 7.0.0 | 7.0.9 | | `neos/neos` | Packagist | From 7.0.0 | 7.0.9 | | `neos/neos` | Packagist | From 7.1.0 | 7.1.7 | | `neos/neos` | Packagist | From 7.1.0 | 7.1.7 | | `neos/neos` | Packagist | From 7.2.0 | 7.2.6 | | `neos/neos` | Packagist | From 7.2.0 | 7.2.6 | | `neos/neos` | Packagist | From 7.3.0 | 7.3.4 | | `neos/neos` | Packagist | From 7.3.0 | 7.3.4 | | `neos/neos` | Packagist | From 8.0.0 | 8.0.2 | | `neos/neos` | Packagist | From 8.0.0 | 8.0.2 | | `neos` | Bitnami | From 3.3.0 | 5.3.10, 7.0.9, 7.1.7, 7.2.6, 7.3.4, 8.0.2 | Products: Neos Neos Cms. ## How do I fix CVE-2022-30429? Upgrade neos/neos to a fixed version for your release line: 4.4.0, 5.3.10, 7.0.9 or 7.1.7. ## Is CVE-2022-30429 being exploited? There is no known exploitation of CVE-2022-30429 in the wild and no public exploit code. ## Other vulnerabilities in n/a - [CVE-2023-37611](https://insights.sbomify.com/CVE-2023-37611/): Neos CMS Cross Site Scripting vulnerability (medium 5.4) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2022-30429 and fix it if it is affected. What it is: CVE-2022-30429 is a medium-severity cross-site scripting vulnerability in n/a, published on 2 Jun 2022. 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 CVE-2022-30429 in the wild and no public exploit code. Affected packages and fixed versions: - neos/neos (Packagist): affected from 3.3.0; fixed in 4.4.0 - neos/neos (Packagist): affected from 3.3.0; fixed in 4.4.0 - neos/neos (Packagist): affected from 5.3.0; fixed in 5.3.10 - neos/neos (Packagist): affected from 5.3.0; fixed in 5.3.10 - neos/neos (Packagist): affected from 7.0.0; fixed in 7.0.9 - neos/neos (Packagist): affected from 7.0.0; fixed in 7.0.9 - neos/neos (Packagist): affected from 7.1.0; fixed in 7.1.7 - neos/neos (Packagist): affected from 7.1.0; fixed in 7.1.7 - neos/neos (Packagist): affected from 7.2.0; fixed in 7.2.6 - neos/neos (Packagist): affected from 7.2.0; fixed in 7.2.6 - neos/neos (Packagist): affected from 7.3.0; fixed in 7.3.4 - neos/neos (Packagist): affected from 7.3.0; fixed in 7.3.4 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/CVE-2022-30429/ (Markdown: https://insights.sbomify.com/CVE-2022-30429/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2022-30429 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-30429 - OSV: https://osv.dev/vulnerability/CVE-2022-30429 --- From sbomify Insights: https://insights.sbomify.com/CVE-2022-30429/ Summaries are generated and may contain mistakes; the official description above is the record.