Is alexusmai/laravel-file-manager 2.2 vulnerable?

Composer · 3 releases from 2.2.1 to 2.2.3 · latest alexusmai/laravel-file-manager is 3.3.3 · checked 18 Nov 2026

Yes: 2 known advisories

Yes. alexusmai/laravel-file-manager 2.2.3, the last 2.2 release, is affected by 2 known security advisories (1 high, 1 low), including CVE-2025-65346, CVE-2025-65345. At least one has no fixed release yet.

Is your project on an affected alexusmai/laravel-file-manager?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Advisories affecting alexusmai/laravel-file-manager 2.2.3

  • HighCVE-2025-65346GHSA-q5hg-wppq-r2cc4 Dec 2025

    alexusmai laravel-file-manager is vulnerable to Directory Traversal via the unzip/extraction functionality

    Affected
    <=3.3.1
    Fixed in
    No fix released
  • LowCVE-2025-65345GHSA-rr44-8j7r-jg2q3 Dec 2025

    alexusmai laravel-file-manager is vulnerable to Directory Traversal

    Affected
    <=3.3.1
    Fixed in
    No fix released

Every alexusmai/laravel-file-manager 2.2.x release

Affected: 2.2.1 to 2.2.3. Latest alexusmai/laravel-file-manager: 3.3.3.

VersionKnown advisories
alexusmai/laravel-file-manager 2.2.3CVE-2025-65346, CVE-2025-65345
alexusmai/laravel-file-manager 2.2.2CVE-2025-65346, CVE-2025-65345
alexusmai/laravel-file-manager 2.2.1CVE-2025-65346, CVE-2025-65345

Which of your client projects are still on alexusmai/laravel-file-manager 2.2?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact alexusmai/laravel-file-manager version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Other alexusmai/laravel-file-manager versions

Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Composer registry. Refreshed daily.