CVE-2022-30429
MEDIUMCVE-2022-30429 is a medium-severity (CVSS 5.4) Cross-site Scripting (XSS) vulnerability in neos/neos. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether CVE-2022-30429 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Neos CMS vulnerable to XSS in various backend modules
Blast Radius
neos/neos🐘neos/neos🐘neos/neos🐘neos/neos🐘neos/neos🐘neos/neos🐘neos/neosReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | neos/neos | ≥ 3.3.0&&< 4.4.0 | 4.4.0 |
| 🐘Packagist | neos/neos | ≥ 5.3.0&&< 5.3.10 | 5.3.10 |
| 🐘Packagist | neos/neos | ≥ 7.0.0&&< 7.0.9 | 7.0.9 |
| 🐘Packagist | neos/neos | ≥ 7.1.0&&< 7.1.7 | 7.1.7 |
| 🐘Packagist | neos/neos | ≥ 7.2.0&&< 7.2.6 | 7.2.6 |
| 🐘Packagist | neos/neos | ≥ 7.3.0&&< 7.3.4 | 7.3.4 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for neos/neos. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update neos/neos to 4.4.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-30429 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2022-30429 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2022-30429. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2022-30429 in your dependencies?
O3 detects CVE-2022-30429 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.