Composer typo3/cms-frontend has 4 known advisories in the phpwarden feed. Feed 2026.10.28.3, updated 2026-10-28.
| CVE | Title | Severity | CVSS | Affected | Fixed in |
|---|---|---|---|---|---|
| CVE-2010-5098 | TYPO3 Cross-site scripting (XSS) vulnerability in the FORM content object | low | 0.0 | >=4.2.0 and <4.2.16 or >=4.4.0 and <4.4.5 or >=4.3.0 and <4.3.9 | 4.2.16, 4.4.5, 4.3.9 |
| CVE-2010-5097 | TYPO3 Cross-site scripting (XSS) vulnerability in the click enlarge functionality | low | 0.0 | >=4.3.0 and <4.3.9 or >=4.4.0 and <4.4.5 | 4.3.9, 4.4.5 |
| CVE-2010-3667 | TYPO3 is vulnerable to Spam Abuse in the native form content element | medium | 5.3 | <4.1.14 or >=4.2.0 and <4.2.13 or >=4.3.0 and <4.3.4 or >=4.4.0 and <4.4.1 | 4.1.14, 4.2.13, 4.3.4, 4.4.1 |
| CVE-2010-3670 | TYPO3 is vulnerable to insecure randomness during hash generation in forgot password function | medium | 4.8 | <4.3.4 or >=4.4.0 and <4.4.1 | 4.3.4, 4.4.1 |
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