Unrestricted Upload of File with Dangerous Type in unisharp/laravel-filemanager

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

6.7 · CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:L

EPSS

• CVE-2021-23814: 1.83% estimated exploitation activity in the next 30 days; percentile 78.89 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

This affects the package unisharp/laravel-filemanager prior to version 2.6.2. The upload() function does not sufficiently validate the file type when uploading. An attacker may be able to reproduce the following steps: - Install a package with a web Laravel application. - Navigate to the Upload window - Upload an image file, then capture the request - Edit the request contents with a malicious file (webshell) - Enter the path of file uploaded on URL - Remote Code Execution Note: Prevention for bad extensions can be done by using a whitelist in the config file(lfm.php). Corresponding document can be found in the here.

Published by the source

6 Jan 2022, 21:08 UTC

Last modified by the source

22 Apr 2024, 19:10 UTC

Source last checked

26 Oct 2026, 14:19 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-f8x6-m9f5-ffp8

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2021-23814

Advisory: Unrestricted Upload of File with Dangerous Type in unisharp/laravel-filemanager
IDs: CVE-2021-23814, GHSA-f8x6-m9f5-ffp8
Record: https://patchnext.com/advisories/cve-2021-23814 (revision 1, source checked 26 Oct 2026, 14:19 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: unisharp/laravel-filemanager 2.6.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist unisharp/laravel-filemanager: affected < 2.6.2; fixed in 2.6.2

## Suggested inspection (read-only)
- Packagist unisharp/laravel-filemanager: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on unisharp/laravel-filemanager.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-f8x6-m9f5-ffp8 (GitHub-reviewed advisory GHSA-f8x6-m9f5-ffp8 lists affected ranges: Packagist unisharp/laravel-filemanager >=0 <2.6.2)

Commands are suggestions: review each one before running it.