# CVE-2025-7900: Insecure Direct Object Reference in extension "femanager" (femanager)

> Attackers can modify user data without authorization due to insecure direct object references in the TYPO3 femanager extension.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 Jul 2025
- **Updated:** 22 Jul 2025
- **Also known as:** GHSA-rc5f-3hfv-jxp2

## What is CVE-2025-7900?

CVE-2025-7900 is a medium-severity missing authorization vulnerability in Typo3 Typo3, published on 22 Jul 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2025-7900?

6 open source packages ship an affected version, including in2code/femanager. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `in2code/femanager` | Packagist | All versions | 6.4.2 |
| `in2code/femanager` | Packagist | All versions | 6.4.2 |
| `in2code/femanager` | Packagist | From 7.0.0 | 7.5.3 |
| `in2code/femanager` | Packagist | From 7.0.0 | 7.5.3 |
| `in2code/femanager` | Packagist | From 8.0.0 | 8.3.1 |
| `in2code/femanager` | Packagist | From 8.0.0 | 8.3.1 |

Products: Typo3 Typo3.

## How do I fix CVE-2025-7900?

Upgrade in2code/femanager to a fixed version for your release line: 6.4.2, 7.5.3 or 8.3.1.

## Is CVE-2025-7900 being exploited?

There is no known exploitation of CVE-2025-7900 in the wild and no public exploit code.

## Other vulnerabilities in Typo3 Typo3

- [CVE-2009-0258](https://insights.sbomify.com/CVE-2009-0258/): Indexed Search Engine for TYPO3 Command Execution via Metacharacter Injection (critical 10.0)
- [CVE-2011-3583](https://insights.sbomify.com/CVE-2011-3583/): Typo3 SQL injection due to faulty prepared statements (critical 9.8)
- [CVE-2011-4628](https://insights.sbomify.com/CVE-2011-4628/): Typo3 Authentication Bypass (critical 9.8)
- [CVE-2023-24814](https://insights.sbomify.com/CVE-2023-24814/): Persisted Cross-Site Scripting in Frontend Rendering in typo3 (high 8.8)
- [CVE-2021-41113](https://insights.sbomify.com/CVE-2021-41113/): Cross-Site-Request-Forgery in Backend URI Handling in Typo3 (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-7900 and fix it if it is affected.

What it is: CVE-2025-7900 is a medium-severity missing authorization vulnerability in Typo3 Typo3, published on 22 Jul 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-7900 in the wild and no public exploit code.

Affected packages and fixed versions:
- in2code/femanager (Packagist): affected all versions; fixed in 6.4.2
- in2code/femanager (Packagist): affected all versions; fixed in 6.4.2
- in2code/femanager (Packagist): affected from 7.0.0; fixed in 7.5.3
- in2code/femanager (Packagist): affected from 7.0.0; fixed in 7.5.3
- in2code/femanager (Packagist): affected from 8.0.0; fixed in 8.3.1
- in2code/femanager (Packagist): affected from 8.0.0; fixed in 8.3.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-7900/ (Markdown: https://insights.sbomify.com/CVE-2025-7900/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-7900
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-7900
- OSV: https://osv.dev/vulnerability/CVE-2025-7900

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-7900/
Summaries are generated and may contain mistakes; the official description above is the record.