CVE-2026-77146: TYPO3-EXT-SA-2026-024: Broken Access Control in extension "femanager" (femanager)

unknown Affects in2code/femanager. Feed 2026.10.29.4, updated 2026-10-29; CVE published 2026.

TYPO3-EXT-SA-2026-024: Broken Access Control in extension "femanager" (femanager)

Package: in2code/femanager Composer
Affected versions: >=8.0.0 and <8.4.2
Fixed in: 8.4.2
Severity: unknown
Exploitation: not on CISA KEV · EPSS 0% (36.1th percentile)
Source: friendsofphp

References

https://news.typo3.com/security/advisory/typo3-ext-sa-2026-024

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-2014-6292 medium TYPO3 femanager extension allows remote frontend users to modify or delete records of othe same package: in2code/femanager
CVE-2021-36787 medium Cross-site Scripting in the femanager TYPO3 extension same package: in2code/femanager
CVE-2022-44543 medium TYPO3 Extension femanager vulnerable to Broken Access Control same package: in2code/femanager
CVE-2023-25013 high Broken Access Control in 3rd party TYPO3 extension "femanager" same package: in2code/femanager
CVE-2023-25014 high Broken Access Control in 3rd party TYPO3 extension "femanager" same package: in2code/femanager
CVE-2026-77134 unknown TYPO3-EXT-SA-2026-024: Broken Access Control in extension "femanager" (femanager) same package: in2code/femanager