# CVE-2025-32807: Path traversal in FusionDirectory

> Remote attackers can read arbitrary files ending in .png, .svg, or .xpm via the icon parameter in geticon.php.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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:** No
- **Published:** 10 Apr 2025
- **Updated:** 11 Apr 2025
- **Also known as:** DEBIAN-CVE-2025-32807, GHSA-chj6-x555-wh22, UBUNTU-CVE-2025-32807

## What is CVE-2025-32807?

CVE-2025-32807 is a medium-severity path traversal vulnerability in FusionDirectory, published on 10 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A path traversal vulnerability in FusionDirectory before 1.5 allows remote attackers to read arbitrary files on the host that end with .png (and .svg or .xpm for some configurations) via the icon parameter of a GET request to geticon.php.

Weakness: CWE-24 (Path Traversal: '../filedir')

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


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

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

## Is CVE-2025-32807 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-32807 is a medium-severity path traversal vulnerability in FusionDirectory, published on 10 Apr 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-32807 in the wild and no public exploit code.

Affected product: FusionDirectory. No package-level version data is available, so check the vendor advisory linked from the reference page.

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

## Sources

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

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