UniSharp Laravel File Manager v2.0.0-alpha7 and v2.0 contain an arbitrary file upload vulnerability that allows authenticated attackers to upload malicious files by sending multipart form data to the upload endpoint. Attackers can upload PHP files with the type parameter set to Files and execute arbitrary code by accessing the uploaded file through the working directory path.
Security readout for executives and security teams
Plain-English summary
This flaw affects UniSharp Laravel File Manager 2.0.0-alpha7 and 2.0. An authenticated user can upload a malicious file and potentially run code on the server. For businesses, the risk is highest where this package is exposed in production and accessible to low-privileged users.
Executive priority
Prioritize within normal emergency patching for exposed production systems. The combination of authenticated remote code execution potential and public exploit information creates meaningful business risk, especially for customer-facing Laravel applications.
Technical view
CVE-2019-25673 is a CWE-434 arbitrary file upload issue in UniSharp Laravel File Manager. The CVSS 3.1 score is 8.8, reflecting network access, low complexity, required authentication, and high confidentiality, integrity, and availability impact. Public references include an Exploit-DB entry, but the provided sources do not show confirmed active exploitation.
Likely exposure
Exposure is likely limited to Laravel applications using UniSharp Laravel File Manager 2.0.0-alpha7 or 2.0. Risk increases if the file manager is reachable from the internet or available to broadly assigned authenticated accounts.
Exploitation context
The issue requires authentication, but no user interaction. Public exploit information exists, so vulnerable internet-facing deployments should be treated as high priority. CISA KEV status is not indicated in the provided data, and active exploitation is not confirmed by the sources.
Researcher notes
The source bundle names affected versions inconsistently as v2.0.0-alpha7, v2.0, and affected version 2.0.0. No authoritative fixed version is provided here. Avoid assuming broader Laravel File Manager versions are vulnerable without confirming against vendor or advisory data.
Mitigation direction
Identify applications using UniSharp Laravel File Manager 2.0.0-alpha7 or 2.0.
Check vendor repository and advisories for fixed versions or official remediation.
Restrict access to trusted administrators until remediation is confirmed.
Disable or remove the file manager if it is not required.
Review upload handling and block executable server-side file types.
Validation and detection
Review composer manifests and lock files for the affected package and version.
Confirm whether file manager routes are internet-facing or internally restricted.
Inspect upload directories for unexpected executable files.
Review web and application logs for suspicious upload and file access activity.
Validate remediation against current vendor guidance before closing the finding.
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-434: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection 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.
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.
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
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.
2CVSS vectors
3Timeline events
1ADP providers
5Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: total
CVSS vector scores
2 official scores
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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-434 · source CWE mapping
Unrestricted Upload of File with Dangerous Type
Unrestricted Upload of File with Dangerous Type represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.