# CVE-2025-46002: Filemanager is vulnerable to Relative Path Traversal through filemanager.php

> Attackers can execute directory traversal via crafted HTTP requests to the filemanager.php endpoint, potentially reading or modifying files.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Jul 2025
- **Updated:** 18 Jul 2025
- **Also known as:** GHSA-r7q6-6fmq-mx4c

## What is CVE-2025-46002?

CVE-2025-46002 is a medium-severity path traversal vulnerability in n/a, published on 18 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue in Filemanager v2.5.0 and below allows attackers to execute a directory traversal via sending a crafted HTTP request to the filemanager.php endpoint.

Weakness: CWE-23 (Relative Path Traversal)

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

2 open source packages ship an affected version, including simogeo/filemanager. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `simogeo/filemanager` | Packagist | All versions to 2.5.0 | None |
| `simogeo/filemanager` | Packagist | All versions to 2.5.0 | None |

Products: Simogeo Filemanager.

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

No fix has been published for CVE-2025-46002 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-46002 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-46002 exists.

## Other vulnerabilities in n/a

- [CVE-2025-46001](https://insights.sbomify.com/CVE-2025-46001/): simogeo/filemanager arbitrary file upload vulnerability (critical 9.8)
- [CVE-2025-46000](https://insights.sbomify.com/CVE-2025-46000/): File upload in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-46002 is a medium-severity path traversal vulnerability in n/a, published on 18 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-46002 exists.

Affected packages and fixed versions:
- simogeo/filemanager (Packagist): affected all versions up to 2.5.0; no fix listed
- simogeo/filemanager (Packagist): affected all versions up to 2.5.0; no fix listed

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-46002/ (Markdown: https://insights.sbomify.com/CVE-2025-46002/index.md)
```

## Sources

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

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