Is derhansen/sf_event_mgt vulnerable?

Composer derhansen/sf_event_mgt has 4 known advisories in the phpwarden feed. Feed 2026.10.29.1, updated 2026-10-28.

4advisories
0critical
0on CISA KEV
0no fix recorded
CVETitleSeverityCVSSAffectedFixed in
CVE-2020-25026Information Disclosure in TYPO3 extension sf_event_mgtmedium4.3<4.3.1 or >=5.0.0 and <5.1.14.3.1, 5.1.1
CVE-2026-77128TYPO3-EXT-SA-2026-023: Broken Access Control in extension "Event management and registration" (sf_event_mgt)unknown0.0>=9.0.0 and <9.0.3 or >=8.0.0 and <8.6.2 or >=7.0.0 and <7.9.3 or >=6.0.0 and <6.7.2 or <5.9.39.0.3, 8.6.2, 7.9.3, 6.7.2
CVE-2024-24751derhansen/sf_event_mgt vulnerable to Broken Access Control in Backend Modulemedium4.3>=7.0.0 and <7.4.07.4.0
CVE-2026-77129TYPO3-EXT-SA-2026-023: Server-Side Template Injection in extension "Event management and registration" (sf_event_mgt)unknown0.0>=9.0.0 and <9.0.3 or >=8.0.0 and <8.6.2 or >=7.0.0 and <7.9.3 or >=6.0.0 and <6.7.2 or <5.9.39.0.3, 8.6.2, 7.9.3, 6.7.2

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
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.