LiveActive security incident?Get immediate response
CVE Record

CVE-2021-23814: This affects versions of the package unisharp/laravel-filemanager before 2.6.2.

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).

MediumCVSS 6.7Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2021-23814 is a file upload validation weakness in unisharp/laravel-filemanager before 2.6.2. In vulnerable Laravel applications, an authenticated user could potentially upload a dangerous file through the upload feature and gain code execution. Business risk is moderate because exploitation requires privileges and user interaction, but impact can be serious.

Executive priority

Treat this as a moderate-priority remediation for affected Laravel systems. It is not KEV-listed, but successful exploitation could compromise application data and integrity. Prioritize internet-facing or broadly accessible admin environments first.

Technical view

The package’s upload() handling did not sufficiently validate uploaded file type before version 2.6.2. The CVSS 3.1 score is 6.7 with network access, high attack complexity, low privileges, required user interaction, and high confidentiality and integrity impact. The weakness is mapped to CWE-94.

Likely exposure

Exposure is likely limited to Laravel applications using unisharp/laravel-filemanager versions before 2.6.2, especially where upload functionality is reachable by authenticated users. The bundle does not identify other affected products or platforms.

Exploitation context

The source bundle describes a malicious file upload leading to remote code execution. CISA KEV status is false, so there is no provided evidence of known active exploitation. The CVSS vector includes proof-of-concept exploit maturity, but not confirmed in-the-wild use.

Researcher notes

The evidence supports vulnerable versions before 2.6.2 and insufficient upload file-type validation. The affected range in the bundle is imprecise, so dependency verification should use package metadata, release notes, and vendor issue context. Avoid assuming unrelated Laravel file managers are affected.

Mitigation direction

  • Upgrade unisharp/laravel-filemanager to version 2.6.2 or later.
  • Configure allowed extensions with a whitelist in lfm.php as noted by the CVE description.
  • Restrict access to file manager upload functionality to trusted users only.
  • Review vendor release notes and issue discussion before deploying compensating controls.

Validation and detection

  • Inventory Laravel applications for unisharp/laravel-filemanager dependency versions below 2.6.2.
  • Check whether file manager upload routes are exposed to authenticated users.
  • Review lfm.php for an explicit allowed-extension whitelist.
  • Inspect web-accessible upload directories for unexpected executable file types.
Prepared
Confidence
high
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-94: Code execution behavior lookup

Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-23814 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.7 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
7Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.7CVSS 3.1MediumCVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:L/E:P1.25.5Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.7Medium
CVSS 3.1 vector shape for CVE-2021-23814Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/aunisharp/laravel-filemanager0Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-94 · source CWE mapping

Improper Control of Generation of Code ('Code Injection')

Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.