typo3/cms-scheduler vulnerabilities
TYPO3 CMS Scheduler - Schedule tasks to run once or periodically at a specific time.
- Registry
- Composer
- Latest
- 14.3.12
- License
- GPL-2.0-or-later
1 known advisory
The latest version, 14.3.12, is not affected by any of them. Projects on older versions may be.
Update to the latest version:
composer require typo3/cms-scheduler:^14.3.12Is your project on an affected typo3/cms-scheduler?
Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Security advisories for typo3/cms-scheduler
TYPO3 Scheduler Module vulnerable to Cross-Site Request Forgery
- Affected
- >=11.0.0 <11.5.42
- Fixed in
- 11.5.42
Is your typo3/cms-scheduler version vulnerable?
- typo3/cms-scheduler 14.3No known advisories in 14.3.12
- typo3/cms-scheduler 14.2No known advisories in 14.2.0
- typo3/cms-scheduler 14.1No known advisories in 14.1.1
- typo3/cms-scheduler 14.0No known advisories in 14.0.2
- typo3/cms-scheduler 13.4No known advisories in 13.4.40
- typo3/cms-scheduler 13.3No known advisories in 13.3.1
- typo3/cms-scheduler 13.2No known advisories in 13.2.1
- typo3/cms-scheduler 13.1No known advisories in 13.1.1
- typo3/cms-scheduler 13.0No known advisories in 13.0.1
- typo3/cms-scheduler 12.4No known advisories in 12.4.45
- typo3/cms-scheduler 12.3No known advisories in 12.3.0
- typo3/cms-scheduler 12.2No known advisories in 12.2.0
- typo3/cms-scheduler 12.1No known advisories in 12.1.3
- typo3/cms-scheduler 12.0No known advisories in 12.0.0
Which of your client projects still run an old typo3/cms-scheduler?
NPMscan reads the composer.lock in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other Composer packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the Composer registry.