CVE-2024-55924: TYPO3 Scheduler Module vulnerable to Cross-Site Request Forgery

high Affects typo3/cms-scheduler. Feed 2026.10.29.4, updated 2026-10-29; published 2025-01-14; advisory modified 2025-05-21.

TYPO3 Scheduler Module vulnerable to Cross-Site Request Forgery

Package: typo3/cms-scheduler Composer
Affected versions: >=11.0.0 and <11.5.42
Fixed in: 11.5.42
Severity: high CVSS 8.0
Exploitation: not on CISA KEV · EPSS 0% (18.9th percentile)
Published: 2025-01-14
Source: osv.dev

References

CWE-352 CWE-749

NVD record typo3/cms-scheduler advisories

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.

# PHP projects (recommended)
composer require --dev phpwarden/phpwarden
# then
vendor/bin/phpwarden deps composer.lock

# or, without Composer
pipx install phpwarden   &&   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

Related advisories

CVE-2019-9787 high WordPress before 5.1.1 does not properly filter comment content, leading to Remote Code Ex same weakness: CWE-352
CVE-2016-6897 medium Cross-site request forgery (CSRF) vulnerability in the wp_ajax_update_plugin function in w same weakness: CWE-352
CVE-2022-1020 critical The Product Table for WooCommerce (wooproducttable) WordPress plugin before 3.1.2 does not same weakness: CWE-352
CVE-2019-12616 medium phpMyAdmin CSRF Vulnerability same weakness: CWE-352
CVE-2020-5776 high Cross-Site Request Forgery in MAGMI same weakness: CWE-352
CVE-2022-1574 critical The HTML2WP WordPress plugin through 1.0.0 does not have authorisation and CSRF checks whe same weakness: CWE-352