How severe is GHSA-rc5f-3hfv-jxp2?

No CVSS score has been assigned to GHSA-rc5f-3hfv-jxp2 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-rc5f-3hfv-jxp2?

GHSA-rc5f-3hfv-jxp2 affects the following packages: in2code/femanager (Packagist), in2code/femanager (Packagist), in2code/femanager (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-rc5f-3hfv-jxp2?

Update in2code/femanager to 6.4.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rc5f-3hfv-jxp2 is resolved across your whole dependency graph.

How do I detect GHSA-rc5f-3hfv-jxp2 in my Packagist dependencies?

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.

How do I mitigate GHSA-rc5f-3hfv-jxp2 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.

Is GHSA-rc5f-3hfv-jxp2 actively exploited in the wild?

No public exploit code has been indexed for GHSA-rc5f-3hfv-jxp2 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-rc5f-3hfv-jxp2?

GHSA-rc5f-3hfv-jxp2 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 17th 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.

What type of vulnerability is GHSA-rc5f-3hfv-jxp2?

GHSA-rc5f-3hfv-jxp2 is classified as CWE-639 (CWE-639). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-rc5f-3hfv-jxp2 published, and has it been updated?

GHSA-rc5f-3hfv-jxp2 was published on July 22, 2025 and was last updated on July 22, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

Not in CISA KEV

Femanager extension for TYPO3 allows Insecure Direct Object ReferenceGHSA-rc5f-3hfv-jxp2

Fix: in2code-de/femanager@9bd9fbd

GHSA-rc5f-3hfv-jxp2 is a CWE-639 vulnerability in in2code/femanager. A fix is available for in2code/femanager — see the affected versions and patch details below.

Also known asCVE-2025-7900

Published

Jul 22, 2025

Updated

Jul 22, 2025

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

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-rc5f-3hfv-jxp2.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs17th percentile — riskier than 17% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

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

The femanager extension for TYPO3 allows Insecure Direct Object Reference resulting in unauthorized modification of userdata. This issue affects femanager version 6.4.1 and below, 7.0.0 to 7.5.2 and 8.0.0 to 8.3.0.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`in2code/femanager`	all versions	6.4.2`composer require in2code/femanager:^6.4.2`
🐘Packagist	`in2code/femanager`	≥ 7.0.0&&< 7.5.3	7.5.3`composer require in2code/femanager:^7.5.3`
🐘Packagist	`in2code/femanager`	≥ 8.0.0&&< 8.3.1	8.3.1`composer require in2code/femanager:^8.3.1`

Affected Products

1 product · 3 configurations

Application

typo3typo3

≥ 8.0.0 && ≤ 8.3.0

range

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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update in2code/femanager to 6.4.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rc5f-3hfv-jxp2 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.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-rc5f-3hfv-jxp2 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works