CVE-2022-44543 is a medium-severity (CVSS 6.5) vulnerability in in2code/femanager. A fix is available for in2code/femanager — see the affected versions and patch details below.
TYPO3 Extension femanager vulnerable to Broken Access Control
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
in2code/femanager🐘in2code/femanager🐘in2code/femanagerReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
The TYPO3 Extension femanager prior to versions 5.5.2, 6.3.3, and 7.0.1 is vulnerable to broken access control. The usergroup.inList validation can be bypassed resulting in new frontend users created by the extension may be members of groups that are restricted. The vulnerability is only exploitable if the field usergroup is available in the registration form. Versions 5.5.2, 6.3.3, and 7.0.1 contain patches.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | in2code/femanager | ≥ 7.0.0&&< 7.0.1 | 7.0.1composer require in2code/femanager:^7.0.1 |
| 🐘Packagist | in2code/femanager | ≥ 6.0.0&&< 6.3.3 | 6.3.3composer require in2code/femanager:^6.3.3 |
| 🐘Packagist | in2code/femanager | all versions | 5.5.2composer require in2code/femanager:^5.5.2 |
Affected Products
femanagerin2codeDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for in2code/femanager, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update in2code/femanager to 7.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-44543 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.
Frequently Asked Questions
Is CVE-2022-44543 in your dependencies?
Find it across Packagist, including transitive dependencies.