Is in2code/femanager 7.3 vulnerable?
Composer · 1 release from 7.3.0 to 7.3.0 · latest in2code/femanager is 13.4.1 · checked 18 Nov 2026
Yes: 2 known advisories
Yes. in2code/femanager 7.3.0, the last 7.3 release, is affected by 2 known security advisories (2 medium), including CVE-2025-7900, CVE-2025-48202. Upgrade to 7.5.3 or later to fix all of them.
composer require in2code/femanager:^7.5.3Is your project on an affected in2code/femanager?
Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting in2code/femanager 7.3.0
Femanager extension for TYPO3 allows Insecure Direct Object Reference
- Affected
- <6.4.2 · >=7.0.0 <7.5.3 · >=8.0.0 <8.3.1
- Fixed in
- 6.4.2, 7.5.3, 8.3.1
The femanager TYPO3 extension allows Insecure Direct Object Reference
- Affected
- >=8.0.0 <8.2.2 · >=7.0.0 <7.4.2 · >=6.0.0 <6.4.1 · >=5.5.0 <5.5.5
- Fixed in
- 5.5.5, 6.4.1, 7.4.2, 8.2.2
Which of your client projects are still on in2code/femanager 7.3?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact in2code/femanager version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other in2code/femanager versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Composer registry. Refreshed daily.