# CVE-2025-48207: reint_downloadmanager TYPO3 Extension is susceptible to Insecure Direct Object Reference

> Attackers can access unauthorized files via insecure direct object references in the reint_downloadmanager extension for TYPO3.

- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 21 May 2025
- **Updated:** 21 May 2025
- **Also known as:** GHSA-jjwh-4x89-7f5w

## What is CVE-2025-48207?

CVE-2025-48207 is a high-severity missing authorization vulnerability in TYPO3 reint downloadmanager extension, published on 21 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The reint_downloadmanager extension through 5.0.0 for TYPO3 allows Insecure Direct Object Reference.

Weakness: CWE-425 (Direct Request)

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

4 open source packages ship an affected version, including renolit/reint-downloadmanager.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `renolit/reint-downloadmanager` | Packagist | All versions | 4.0.2 |
| `renolit/reint-downloadmanager` | Packagist | All versions | 4.0.2 |
| `renolit/reint-downloadmanager` | Packagist | From 5.0.0 | 5.0.1 |
| `renolit/reint-downloadmanager` | Packagist | From 5.0.0 | 5.0.1 |

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

Upgrade renolit/reint-downloadmanager to a fixed version for your release line: 4.0.2 or 5.0.1.

## Is CVE-2025-48207 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-48207 is a high-severity missing authorization vulnerability in TYPO3 reint downloadmanager extension, published on 21 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-48207 in the wild and no public exploit code.

Affected packages and fixed versions:
- renolit/reint-downloadmanager (Packagist): affected all versions; fixed in 4.0.2
- renolit/reint-downloadmanager (Packagist): affected all versions; fixed in 4.0.2
- renolit/reint-downloadmanager (Packagist): affected from 5.0.0; fixed in 5.0.1
- renolit/reint-downloadmanager (Packagist): affected from 5.0.0; fixed in 5.0.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-48207/ (Markdown: https://insights.sbomify.com/CVE-2025-48207/index.md)
```

## Sources

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

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