What is CVE-2025-7900?

CVE-2025-7900 is a medium-severity security vulnerability in in2code/femanager (composer), affecting versions < 6.4.2. It is fixed in 6.4.2, 7.5.3, 8.3.1.

Which versions of in2code/femanager are affected by CVE-2025-7900?

in2code/femanager (composer) versions < 6.4.2 is affected.

Is there a fix for CVE-2025-7900?

Yes. CVE-2025-7900 is fixed in 6.4.2, 7.5.3, 8.3.1. Upgrade to this version or later.

Is CVE-2025-7900 exploitable, and should I be worried?

Whether CVE-2025-7900 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2025-7900 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2025-7900 in in2code/femanager | Intelligent Application Security

Q: Which versions of in2code/femanager are affected by CVE-2025-7900?

in2code/femanager (composer) versions < 6.4.2 is affected.

Q: Is there a fix for CVE-2025-7900?

Yes. CVE-2025-7900 is fixed in 6.4.2, 7.5.3, 8.3.1. Upgrade to this version or later.

Q: Is CVE-2025-7900 exploitable, and should I be worried?

Whether CVE-2025-7900 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2025-7900 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2025-7900?

Upgrade: in2code/femanager to 6.4.2 or later, in2code/femanager to 7.5.3 or later, in2code/femanager to 8.3.1 or later.

Summary

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.

Impact

Affected versions

in2code/femanager (< 6.4.2) in2code/femanager (>= 7.0.0, < 7.5.3) in2code/femanager (>= 8.0.0, < 8.3.1)

Security releases

in2code/femanager → 6.4.2 (composer) in2code/femanager → 7.5.3 (composer) in2code/femanager → 8.3.1 (composer)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

See it in your environment

Remediation advice

Upgrade the following packages to resolve this vulnerability:

in2code/femanager to 6.4.2 or later; in2code/femanager to 7.5.3 or later; in2code/femanager to 8.3.1 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2025-7900? CVE-2025-7900 is a medium-severity security vulnerability in in2code/femanager (composer), affecting versions < 6.4.2. It is fixed in 6.4.2, 7.5.3, 8.3.1.
Which versions of in2code/femanager are affected by CVE-2025-7900? in2code/femanager (composer) versions < 6.4.2 is affected.
Is there a fix for CVE-2025-7900? Yes. CVE-2025-7900 is fixed in 6.4.2, 7.5.3, 8.3.1. Upgrade to this version or later.
Is CVE-2025-7900 exploitable, and should I be worried? Whether CVE-2025-7900 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2025-7900 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2025-7900?
- Upgrade in2code/femanager to 6.4.2 or later
- Upgrade in2code/femanager to 7.5.3 or later
- Upgrade in2code/femanager to 8.3.1 or later

Other vulnerabilities in in2code/femanager

CVE-IDSeverityPackage summary

CVE-2025-48202Mediumin2code/femanager: The femanager TYPO3 extension allows Insecure Direct Object Reference CVE-2023-50459Mediumin2code/femanager: Broken Access Control in extension "femanager" CVE-2023-45023Mediumin2code/femanager: TYPO3 extension femanager Broken Access Control vulnerability CVE-2023-25014Highin2code/femanager: Broken Access Control in 3rd party TYPO3 extension "femanager"CVE-2023-25013Highin2code/femanager: Broken Access Control in 3rd party TYPO3 extension "femanager"