CVE-2022-30429 — neos/neos
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. A fix is available for neos/neos — see the affected versions and patch details below.
Neos CMS vulnerable to XSS in various backend modules
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2022-30429 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,333 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
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.0composer require neos/neos:^4.4.0 |
| 🐘Packagist | neos/neos | ≥ 5.3.0&&< 5.3.10 | 5.3.10composer require neos/neos:^5.3.10 |
| 🐘Packagist | neos/neos | ≥ 7.0.0&&< 7.0.9 | 7.0.9composer require neos/neos:^7.0.9 |
| 🐘Packagist | neos/neos | ≥ 7.1.0&&< 7.1.7 | 7.1.7composer require neos/neos:^7.1.7 |
| 🐘Packagist | neos/neos | ≥ 7.2.0&&< 7.2.6 | 7.2.6composer require neos/neos:^7.2.6 |
| 🐘Packagist | neos/neos | ≥ 7.3.0&&< 7.3.4 | 7.3.4composer require neos/neos:^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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2022-30429 can be triaged on real exposure rather than presence alone.
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 Security finds CVE-2022-30429 across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.