Security readout for executives and security teams
Plain-English summary
This issue lets a logged-in attacker turn a file upload into server-side code execution in alexusmai laravel-file-manager 3.3.1 and earlier. If the file manager is exposed to low-privilege users and uploaded files are executable from the web, compromise could include data theft, site tampering, or service disruption.
Executive priority
Treat this as a high-priority application exposure review. It is not proven actively exploited in the supplied sources, but successful exploitation could give an authenticated user control over the affected web server context.
Technical view
The CVE describes authenticated RCE through upload and rename handling in alexusmai laravel-file-manager 3.3.1 and before. A crafted image-named upload is saved despite apparent client-side validation failure, then renamed to an executable extension and accessed through a public URL. CVSS 3.1 is 8.8, CWE-94.
Likely exposure
Exposure is likely in Laravel applications using alexusmai laravel-file-manager 3.3.1 or earlier, especially where non-administrative authenticated users can access the file manager and uploads are served by a PHP-capable public web path.
Exploitation context
The CVE is not listed as KEV in the provided bundle. The referenced public GitHub page suggests technical detail is public, but the bundle does not prove active exploitation in the wild. Attack requires authentication but no user interaction.
Researcher notes
Affected metadata in the bundle is incomplete, but the title and description name alexusmai laravel-file-manager 3.3.1 and before. Avoid assuming a patched version from the supplied evidence. Validate exposure through dependency inventory, access controls, upload storage behavior, and server execution policy.
Mitigation direction
- Identify whether alexusmai laravel-file-manager is installed and determine the exact version.
- Check the project or vendor guidance for a fixed release or official mitigation.
- Restrict file-manager access to trusted administrators until remediation is confirmed.
- Ensure uploaded files are not served from PHP-executable public paths.
- Review server rules to prevent execution of user-uploaded content.
Validation and detection
- Inventory Laravel applications for alexusmai laravel-file-manager usage and version.
- Review route and authentication controls protecting the file manager interface.
- Check upload storage locations for public PHP execution capability.
- Inspect logs for suspicious upload, rename, or direct access patterns.
- Confirm remediation against official project guidance when available.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-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 lookupExecution 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 lookupFile access behavior lookup
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.
Open ATT&CK lookupCVE-2025-56399 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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.
SSVC decision data
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H2.85.9CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
8.8HighVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/Theethat-Thamwasin/CVE-2025-56399CVE reference, mitre
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
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.