CVE-2025-65345
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedalexusmai 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidencealexusmai laravel-file-manager versions 3.3.1 and below contain a directory traversal vulnerability in the zip/archiving functionality. The affected code fails to properly validate file paths, allowing an attacker to include files from directories outside the intended scope when creating archives by manipulating path traversal sequences.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 3.3.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed version of laravel-file-managerLocate the composer.json file in the laravel-file-manager package directory, or run 'composer show alexusmai/laravel-file-manager' to retrieve the installed version numberAffected if The installed version is 3.3.1 or lower
-
Confirm zip/archive functionality is enabledCheck the laravel-file-manager configuration file (typically config/file-manager.php) for the 'archive' or 'zip' feature setting and verify it is set to enabled or trueAffected if The archive/zip functionality is enabled in the configuration
-
Verify path validation is present in archive logicExamine the archive creation controller or service file within the laravel-file-manager package for code that validates or sanitizes file paths before creating archives, specifically looking for checks that block or strip '..' sequencesAffected if No path validation logic that blocks directory traversal sequences is found in the archive code
-
Review application logs for exploitation attemptsSearch web server and application logs for archive/download requests containing '../' or '..\' sequences targeting the file-manager endpointAffected if Log entries show directory traversal patterns in archive-related requests
-
Check web server access controlsVerify that the web server or application does not have additional access controls that restrict file-manager archive functionality to authorized users onlyAffected if The archive feature is publicly accessible without authentication
You are affected if you have laravel-file-manager version 3.3.1 or lower with the zip/archive functionality enabled and accessible, and no custom path validation is implemented to block directory traversal sequences.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade to a patched version of laravel-file-manager once available, or implement path validation that strips/blocks directory traversal sequences (..) and verifies all paths remain within allowed directories before archiving.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-65345 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-65345 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data