dbcve.org
Laravel FilemanagerFramework / library · Unisharp

CVE-2021-23814

HIGH · 8.8 CVSS v3.1 Published 2021-12-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
This affects versions of the package unisharp/laravel-filemanager before 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: 1. Install a package with a web Laravel application. 2. Navigate to the Upload window 3. Upload an image file, then capture the request 4. Edit the request contents with a malicious file (webshell) 5. 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 [here](https://unisharp.github.io/laravel-filemanager/configfolder-categories).

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 · high confidence

The unisharp/laravel-filemanager package before version 2.6.2 has insufficient file type validation in its upload() function, allowing attackers to upload malicious webshells by intercepting upload requests and modifying file contents, leading to Remote Code Execution.

MitigationUpgrade to version 2.6.2 or later and configure file extension whitelisting in the lfm.php configuration file to restrict uploads to safe, expected file types.

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
Laravel FilemanagerFramework / library
Affected:>= 0.0.0

CVSS 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 checks

Work through these to decide whether this CVE applies to you.

  1. Check installed package version
    Run 'composer show unisharp/laravel-filemanager' or inspect the version listed in your composer.lock file under the laravel-filemanager package entry
    Affected if The installed version is earlier than 2.6.2 (any version from 0.0.0 to 2.6.1 is affected)
  2. Locate the lfm.php configuration file
    Find the laravel-filemanager config file (typically at config/lfm.php) in your project
    Affected if The configuration file does not exist or lacks file extension restrictions
  3. Inspect file extension whitelisting settings
    Open config/lfm.php and look for settings related to file types or extensions, such as 'allowed_extensions', 'file_type_array', or similar fields that control permitted upload types
    Affected if No file extension whitelist is defined, or the whitelist permits executable types like php, phtml, js, or other script extensions
  4. Determine if upload functionality is publicly accessible
    Check your routes/web.php or routes/api.php for file manager routes and verify the middleware applied to them (whether they are protected by auth middleware or exposed publicly)
    Affected if The upload endpoints are accessible without authentication (no auth middleware)

You are affected if your installed version of unisharp/laravel-filemanager is earlier than 2.6.2, or if file extension whitelisting is not properly configured regardless of version.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to version 2.6.2 or later and configure file extension whitelisting in the lfm.php configuration file to restrict uploads to safe, expected file types.

Recommended fix High confidence

unisharp/laravel-filemanager version 2.6.2 or later

  1. Run composer update unisharp/laravel-filemanager to upgrade to the latest version
  2. Alternatively, run composer require unisharp/laravel-filemanager:2.6.2 to specify the fixed version
  3. Verify the upgrade was successful by checking your composer.json or running composer show unisharp/laravel-filemanager
  4. Test the file upload functionality to ensure legitimate uploads still work correctly
  5. If using a whitelist approach as a defense-in-depth measure, configure allowed extensions in config/lfm.php according to the documentation

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Laravel Filemanager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-23814 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-23814 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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