# CVE-2025-65345: alexusmai laravel-file-manager is vulnerable to Directory Traversal

> Attackers can read or modify files outside the intended directory via the zip functionality in the Laravel file manager library.

- **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:** 3 Dec 2025
- **Updated:** 5 Dec 2025
- **Also known as:** GHSA-rr44-8j7r-jg2q

## What is CVE-2025-65345?

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

### Official description

alexusmai laravel-file-manager 3.3.1 and below is vulnerable to Directory Traversal. The zip/archiving functionality allows an attacker to create archives containing files and directories outside the intended scope due to improper path validation.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

2 open source packages ship an affected version, including alexusmai/laravel-file-manager. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `alexusmai/laravel-file-manager` | Packagist | All versions to 3.3.1 | None |
| `alexusmai/laravel-file-manager` | Packagist | All versions to 3.3.1 | None |

Products: Alexusmai Laravel File Manager.

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

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

## Is CVE-2025-65345 being exploited?

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

Public exploit code:

- An authenticated Directory Traversal vulnerability in laravel-file-manager v3.3.1 and below allows attackers with access to the file manager interface to use zip/archiving function to create archives containing files and directories outside the intended scope due to improper path validation. (github_poc): https://github.com/tlekrean/CVE-2025-65345

## Other vulnerabilities in n/a

- [CVE-2025-65346](https://insights.sbomify.com/CVE-2025-65346/): alexusmai laravel-file-manager is vulnerable to Directory Traversal via the unzip/extraction functionality (critical 9.1)
- [CVE-2025-63307](https://insights.sbomify.com/CVE-2025-63307/): Cross-site scripting in n/a (high 8.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-65345 is a medium-severity path traversal vulnerability in n/a, published on 3 Dec 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-65345 in the wild and no public exploit code.

Affected packages and fixed versions:
- alexusmai/laravel-file-manager (Packagist): affected all versions up to 3.3.1; no fix listed
- alexusmai/laravel-file-manager (Packagist): affected all versions up to 3.3.1; 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-65345/ (Markdown: https://insights.sbomify.com/CVE-2025-65345/index.md)
```

## Sources

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

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