Is in2code/femanager 8.2 vulnerable?

Composer · 3 releases from 8.2.0 to 8.2.2 · latest in2code/femanager is 13.4.1 · checked 18 Nov 2026

Yes: 1 known advisory

Yes. in2code/femanager 8.2.2, the last 8.2 release, is affected by 1 known security advisory (1 medium), including CVE-2025-7900. 1 more affects earlier 8.2.x releases. Upgrade to 8.3.1 or later to fix all of them.

Upgrade with:composer require in2code/femanager:^8.3.1

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

Advisories affecting in2code/femanager 8.2.2

  • 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

Fixed within 8.2.x, affecting earlier releases

  • MediumCVE-2025-48202GHSA-xxwr-wv9g-7jw321 May 2025

    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

Every in2code/femanager 8.2.x release

Affected: 8.2.0 to 8.2.2. Latest in2code/femanager: 13.4.1.

VersionKnown advisories
in2code/femanager 8.2.2CVE-2025-7900
in2code/femanager 8.2.1CVE-2025-7900, CVE-2025-48202
in2code/femanager 8.2.0CVE-2025-7900, CVE-2025-48202

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

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.