typo3/cms-recycler
Composer (PHP) package
Overview
Package versions
| Versions | Range | Direct vulnerabilities |
|---|---|---|
| 14.3.3 | and later versions | 0C0H0M0L |
| 14.0.2 | up to 14.3.3 | 0C0H1M0L |
| 14.0.0 | up to 14.0.2 | 0C1H1M0L |
| 13.4.31 | up to 14.0.0 | 0C0H0M0L |
| 13.4.23 | up to 13.4.31 | 0C0H1M0L |
| 13.4.18 | up to 13.4.23 | 0C1H1M0L |
| 13.0.0 | up to 13.4.18 | 0C1H2M0L |
| 12.4.46 | up to 13.0.0 | 0C0H0M0L |
| 12.4.41 | up to 12.4.46 | 0C0H1M0L |
| 12.4.37 | up to 12.4.41 | 0C1H1M0L |
| 12.0.0 | up to 12.4.37 | 0C1H2M0L |
| 11.5.51 | up to 12.0.0 | 0C0H1M0L |
| 11.5.49 | up to 11.5.51 | 0C0H2M0L |
| 11.0.0 | up to 11.5.49 | 0C1H2M0L |
| 10.4.57 | up to 11.0.0 | 0C0H1M0L |
| 10.4.55 | up to 10.4.57 | 0C0H2M0L |
| 10.0.0 | up to 10.4.55 | 0C1H2M0L |
| 9.0.0 | up to 10.0.0 | 0C0H2M0L |
| before 9.0.0 | all earlier versions | 0C0H1M0L |
No known vulnerabilities in 14.3.3 and later versions
Nothing in our data affects this version.
19 ranges in total. Each row is a range of versions with the same vulnerabilities, newest first. The data names only the versions where something changes (first affected, fixed), so the versions in between are a range.
Vulnerabilities · 3
| CVE | Severity | Published | Vulnerable | Fixed in |
|---|---|---|---|---|
| CVE-2026-47349TYPO3-CORE-SA-2026-011: Broken Access Control in Recycler | MEDIUM | 9 Jun 2026 | <10.4.57>=11.0.0, <11.5.51>=12.0.0, <12.4.46>=13.0.0, <13.4.31>=14.0.0, <14.3.3 | 10.4.5711.5.5112.4.4613.4.3114.3.3 |
| CVE-2025-59022TYPO3 CMS Allows Broken Access Control in Recycler Module | HIGH | 13 Jan 2026 | >=14.0.0, <14.0.2>=13.0.0, <13.4.23>=12.0.0, <12.4.41>=11.0.0, <11.5.49>=10.0.0, <10.4.55 | 14.0.213.4.2312.4.4111.5.4910.4.55 |
| CVE-2025-59017TYPO3 backend modules have Broken Access Control | MEDIUM | 9 Sep 2025 | >=9.0.0, <12.4.37>=10.0.0, <12.4.37>=11.0.0, <12.4.37>=12.0.0, <12.4.37>=13.0.0, <13.4.18 | 12.4.3713.4.18 |
OX Radar and Response Center
Find threats in your stack.
OX Radar can check high-priority threats, like critical package CVEs, against your context.
Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.