Vulnerability Database · Packagist · in2code/femanager · Version
in2code/femanager 5.3.1
5.3.1 is affected by 4 vulnerabilities.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to.
Critical 0 High 2 Medium 2 Low 0 Unrated 0
-
Database updated 23/Oct/2026
Concerned about your application's security?
Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.
01 Vulnerabilities affecting this version
in2code/femanager 5.3.1 vulnerabilities
4 vulnerabilities cover in2code/femanager 5.3.1. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| CVE-2023-25014: Broken Access Control in TYPO3 extension "femanager" | 8.6 high | 5.5.3 | 02 Feb 2023 |
| CVE-2023-25013: Broken Access Control in TYPO3 extension "femanager" | 8.6 high | 5.5.3 | 02 Feb 2023 |
| CVE-2025-7900: Insecure Direct Object Reference in in2code/femanager Extension for TYPO3 | 5.3 medium | 6.4.2 | 22 Jul 2025 |
| CVE-2021-36787: Cross-site Scripting in the femanager TYPO3 extension | N/A medium | 5.5.1 | 01 Sep 2021 |
Looking for another version, or everything Vulert holds for in2code/femanager?
Questions
About in2code/femanager 5.3.1
Is in2code/femanager 5.3.1 vulnerable?
Yes. 4 vulnerabilities in the Vulert database cover in2code/femanager 5.3.1: 0 critical, 2 high, 2 medium and 0 low. Each entry above names the fixed version to move to.
How do I monitor in2code/femanager for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the in2code/femanager version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.