Is typo3/neos vulnerable?

Composer typo3/neos has 6 known advisories in the phpwarden feed. Feed 2026.10.29.1, updated 2026-10-28.

6advisories
0critical
0on CISA KEV
0no fix recorded
CVETitleSeverityCVSSAffectedFixed in
GHSA-wr3c-6c22-m9v6Privilege Escalation in TYPO3 Neosmedium4.9>=1.1.0 and <1.1.3 or >=1.2.0 and <1.2.31.1.3, 1.2.3
2015-03-28Privilege Escalation in TYPO3 Neosunknown0.0>=1.1.0 and <1.1.3 or >=1.2.0 and <1.2.31.1.3, 1.2.3
2015-11-23XSS vulnerabilities in Neosunknown0.0>=1.2.0 and <1.2.13 or >=2.0.0 and <2.0.41.2.13, 2.0.4
2019-06-17Information Disclosure Security Noteunknown0.0>=2.3.0 and <2.3.99 or >=3.0.0 and <3.0.20 or >=3.1.0 and <3.1.18 or >=3.2.0 and <3.2.14 or >=3.3.0 and <3.3.23 or >=4.0.0 and <4.0.17 or >=4.1.0 and <4.1.16 or >=4.2.0 and <4.2.12 or >=4.3.0 and <4.3.32.3.99, 3.0.20, 3.1.18, 3.2.14
GHSA-4542-p56h-8xwwCross-Site Scripting (XSS) vulnerabilities in Neoshigh0.0>=1.2.0 and <1.2.13 or >=2.0.0 and <2.0.41.2.13, 2.0.4
GHSA-g4xv-r3qw-v3q2typo3 Information Disclosure Security Notehigh0.0>=2.3.0 and <2.3.99 or >=3.0.0 and <3.0.20 or >=3.1.0 and <3.1.18 or >=3.2.0 and <3.2.14 or >=3.3.0 and <3.3.23 or >=4.0.0 and <4.0.17 or >=4.1.0 and <4.1.16 or >=4.2.0 and <4.2.12 or >=4.3.0 and <4.3.32.3.99, 3.0.20, 3.1.18, 3.2.14

Am I affected?

Find out in one command. phpwarden checks your composer.lock against this advisory and 20,000+ others, ranked by real-world exploitation (CISA KEV + EPSS). Free, offline, open data.

# one-time install
pip install phpwarden

# then
phpwarden deps composer.lock

Or keep it checked automatically: GitHub Action · pre-commit hook · GitLab CI · Laravel artisan command

Install docs   How findings are ranked
A version is vulnerable when it falls inside an affected range and below the fixed version. phpwarden applies these ranges to the exact versions in your lockfile or install, so you only see what applies to you.