/

CVE-2026-50894

Severity:

CRITICAL RISK

(9.8)

Unrestricted File Upload (CWE-434) in easyadmin v2

CVE-2026-50894

Deferred

Vulnerability type

Category:

Unrestricted File Upload

CWE:

CWE-434

Impact:

Remote Code Execution and Server Privilege Compromise

Severity:

CRITICAL RISK

(9.8)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

easyadmin v2.0.2.2 contains an unrestricted file upload vulnerability in its background management interface. An authenticated remote attacker may upload a file containing a dangerous type and, if the server processes or executes it, run arbitrary code with the privileges of the affected service.

Affected context

The vulnerability occurs in deployments where authenticated users can reach the background management upload functionality and uploaded files are not sufficiently restricted by type, content, storage location, or execution behavior. Risk is higher when the upload directory is web-accessible or when the application interprets uploaded content as executable code.

Exploit preconditions

  • Attack surface: Background management interface file-upload functionality
  • Required access: Valid authentication and authorization to reach the affected upload operation
  • Trigger point: Processing, storing, or subsequently requesting a crafted uploaded file
  • Why exploitation is possible: File type and execution behavior are not sufficiently constrained, allowing a dangerous file to reach a context where server-side code may be executed

Why this happens

The underlying bug is an unrestricted file upload, mapped to CWE-434. The application accepts uploaded content without reliably enforcing an allowlist of permitted types, validating file content independently of its name, and isolating stored files from executable server paths. This insecure pattern can allow attacker-controlled files to be interpreted by the server rather than treated solely as inert data.

Potential impact

  • An attacker may execute arbitrary code on the affected server
  • The application process could be compromised
  • Sensitive application data may be accessed or modified
  • Server privileges could be abused for persistence or lateral movement
  • Service availability and integrity could be disrupted

General mitigation guidance

Mitigation generally focuses on treating uploads as untrusted data and

preventing uploaded content from becoming executable.

Common defensive patterns include:

  • Permit only narrowly defined business-required file types using an allowlist
  • Validate file signatures and content in addition to filename extensions and MIME types
  • Store uploads outside executable and web-served directories where possible
  • Generate server-side filenames and prevent user-controlled path components
  • Apply size, rate, and quota limits to upload operations
  • Disable script execution in upload locations and serve files with safe content-disposition behavior
  • Enforce authorization and least privilege for upload and file-processing functions
  • Scan uploaded content where appropriate and isolate processing from core application services

How teams detect issues like this

High-level detection approaches include:

  • Static analysis for upload handlers that trust filename extensions, client-provided MIME types, or user-controlled paths
  • Code review checks for executable storage locations and direct mapping of uploaded files to web routes
  • Runtime monitoring for unusual upload types, executable content, repeated upload failures, and requests for newly uploaded resources
  • Policy enforcement requiring content validation, non-executable storage, and explicit authorization for upload endpoints
  • Automated security review tools can help identify dangerous upload-handling patterns during development

Sources

SourceLink
github.comgithub.com/lilil3333/cve/issues/1
github.comgithub.com/zhongshaofa/easyadmin/

Frequently asked

questions

Yes, an authenticated remote attacker may be able to exploit the issue through

the background management interface when the attacker has permission to use

the affected upload functionality.

Authentication is required according to the vulnerability description. The

account must also have sufficient authorization to reach the vulnerable upload

operation.

Treat uploads as untrusted data, enforce a strict content allowlist, validate

file signatures, store files outside executable paths, and disable execution

in upload directories.

Combine least-privilege authorization with secure upload design, server-side

filename generation, content inspection, non-executable storage, monitoring,

and security-focused code review.

Find out what's already
exploitable in your codebase.