How severe is GHSA-mm8v-wmqx-8h2j?

GHSA-mm8v-wmqx-8h2j has a CVSS score of 8.6/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-mm8v-wmqx-8h2j?

GHSA-mm8v-wmqx-8h2j affects the following packages: in2code/femanager (Packagist), in2code/femanager (Packagist), in2code/femanager (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-mm8v-wmqx-8h2j?

Update in2code/femanager to 5.5.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mm8v-wmqx-8h2j is resolved across your whole dependency graph.

How do I detect GHSA-mm8v-wmqx-8h2j in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for in2code/femanager. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-mm8v-wmqx-8h2j if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-mm8v-wmqx-8h2j?

O3 pinpoints whether GHSA-mm8v-wmqx-8h2j is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-mm8v-wmqx-8h2j actively exploited in the wild?

No public exploit code has been indexed for GHSA-mm8v-wmqx-8h2j yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-mm8v-wmqx-8h2j?

GHSA-mm8v-wmqx-8h2j has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 39th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

When was GHSA-mm8v-wmqx-8h2j published, and has it been updated?

GHSA-mm8v-wmqx-8h2j was published on February 2, 2023 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

GHSA-mm8v-wmqx-8h2j

HIGH

Broken Access Control in 3rd party TYPO3 extension "femanager"

Also known asCVE-2023-25013

Published

Feb 2, 2023

Updated

Nov 8, 2023

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk39th percentile-0.05%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

3 pkgs affected

🐘in2code/femanager🐘in2code/femanager🐘in2code/femanager

Real-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

A missing access check in the InvitationController allows an unauthenticated user with a valid invitation link to set the password of all frontend users.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`in2code/femanager`	all versions	5.5.3
🐘Packagist	`in2code/femanager`	≥ 6.0.0&&< 6.3.4	6.3.4
🐘Packagist	`in2code/femanager`	≥ 7.0.0&&< 7.1.0	7.1.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for in2code/femanager. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update in2code/femanager to 5.5.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mm8v-wmqx-8h2j is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-mm8v-wmqx-8h2j is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-mm8v-wmqx-8h2j. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

A missing access check in the `InvitationController` allows an unauthenticated user with a valid invitation link to set the password of all frontend users.

O3 Security · Impact-Aware SCA

Is GHSA-mm8v-wmqx-8h2j in your dependencies?

O3 detects GHSA-mm8v-wmqx-8h2j across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works