Is in2code/femanager 7.5 vulnerable?

Composer · 6 releases from 7.5.0 to 7.5.5 · latest in2code/femanager is 13.4.1 · checked 18 Nov 2026

No known advisories in the last release

in2code/femanager 7.5.5, the last 7.5 release, has no known advisories. 1 advisory affects earlier 7.5.x releases, so update to 7.5.5.

Update within 7.5:composer require in2code/femanager:^7.5.5

Is your project on an affected in2code/femanager?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Fixed within 7.5.x, affecting earlier releases

  • MediumCVE-2025-7900GHSA-rc5f-3hfv-jxp222 Jul 2025

    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

Every in2code/femanager 7.5.x release

Affected: 7.5.0 to 7.5.2. 7.5.3 and later are not affected. Latest in2code/femanager: 13.4.1.

VersionKnown advisories
in2code/femanager 7.5.5None
in2code/femanager 7.5.4None
in2code/femanager 7.5.3None
in2code/femanager 7.5.2CVE-2025-7900
in2code/femanager 7.5.1CVE-2025-7900
in2code/femanager 7.5.0CVE-2025-7900

Which of your client projects are still on in2code/femanager 7.5?

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.