CVE-2025-65346 json
alexusmai laravel-file-manager is vulnerable to Directory Traversal via the unzip/extraction functionality
published 2025-12-04 11 mo ago modified 2026-11-04 4 d ago also GHSA-q5hg-wppq-r2cc , EUVD-2025-201169
- cvss
- 9.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.0%
- EPSS 1.0% chance of exploitation in 30 days, percentile 63%
- public exploits
- 0
- none known
Summary
alexusmai laravel-file-manager 3.3.1 and below is vulnerable to Directory Traversal. The unzip/extraction functionality improperly allows archive contents to be written to arbitrary locations on the filesystem due to insufficient validation of extraction paths.
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- yes
- Technical impact
- total
- Assessed
- 11 mo ago
Exploit prediction
1.02% chance of exploitation in the next 30 days, higher than 63% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- github.com https://github.com/Theethat-Thamwasin/CVE-2025-65346/blob/main/POC-CVE-65346.md referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 9.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N |
| CNA | 3.1 | 9.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N |
| GitHub | 3.1 | 9.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | alexusmai/laravel-file-manager | <=3.3.1 |
no fix listed |
Classification
- Weakness
-
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory
References
-
github.com
/Theethat-Thamwasin/CVE-2025-65346/blob/main/POC-CVE-65346.md
exploit, web, third-party-advisory
-
github.com
/alexusmai/laravel-file-manager
package, product
-
github.com
/Theethat-Thamwasin/CVE-2025-65346
web, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2025-65346
advisory
Sources
- CVE List CVE-2025-65346
- GitHub Advisory GHSA-q5hg-wppq-r2cc
- NVD CVE-2025-65346
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.