Is alexusmai/laravel-file-manager 3.3 vulnerable?

Composer · 4 releases from 3.3.0 to 3.3.3 · latest alexusmai/laravel-file-manager is 3.3.3 · checked 18 Nov 2026

No known advisories in the last release

alexusmai/laravel-file-manager 3.3.3, the last 3.3 release, has no known advisories. 2 advisories affect earlier 3.3.x releases, so update to 3.3.3.

Update within 3.3:composer require alexusmai/laravel-file-manager:^3.3.3

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

Fixed within 3.3.x, affecting earlier releases

  • 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 3.3.x release

Affected: 3.3.0 to 3.3.1. 3.3.2 and later are not affected.

VersionKnown advisories
alexusmai/laravel-file-manager 3.3.3None
alexusmai/laravel-file-manager 3.3.2None
alexusmai/laravel-file-manager 3.3.1CVE-2025-65346, CVE-2025-65345
alexusmai/laravel-file-manager 3.3.0CVE-2025-65346, CVE-2025-65345

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

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.