GHSA-mm8v-wmqx-8h2j — in2code/femanager
HIGHGHSA-mm8v-wmqx-8h2j is a high-severity (CVSS 8.6) Missing Authentication vulnerability in in2code/femanager. A fix is available for in2code/femanager — see the affected versions and patch details below.
Broken Access Control in 3rd party TYPO3 extension "femanager"
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-mm8v-wmqx-8h2j.
EPSS Exploitation Probability
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.
How urgent is this, really
GHSA-mm8v-wmqx-8h2j plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,238 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
in2code/femanager🐘in2code/femanager🐘in2code/femanagerReal-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
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | in2code/femanager | all versions | 5.5.3composer require in2code/femanager:^5.5.3 |
| 🐘Packagist | in2code/femanager | ≥ 6.0.0&&< 6.3.4 | 6.3.4composer require in2code/femanager:^6.3.4 |
| 🐘Packagist | in2code/femanager | ≥ 7.0.0&&< 7.1.0 | 7.1.0composer require in2code/femanager:^7.1.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for in2code/femanager, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-mm8v-wmqx-8h2j can be triaged on real exposure rather than presence alone.
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
Is GHSA-mm8v-wmqx-8h2j in your dependencies?
O3 Security finds GHSA-mm8v-wmqx-8h2j across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.