/

CVE-2026-94104

Severity:

HIGH RISK

(8.8)

Unrestricted File Upload (CWE-434) in NivoCart File Manager

CVE-2026-94104

Deferred

Vulnerability type

Category:

Unrestricted File Upload

CWE:

CWE-434

Impact:

Remote Code Execution

Severity:

HIGH RISK

(8.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

NivoCart contains an arbitrary file upload vulnerability in the File Manager multi() endpoint, where file extension checks can be bypassed for new filenames or certain chunked uploads. An attacker with view-only back-office access may upload executable PHP content into a web-accessible directory and achieve remote code execution.

Affected context

The vulnerability may occur in NivoCart deployments using the File Manager multi() upload endpoint through version 2.4.0. Risk is higher when the endpoint accepts new filenames or chunked uploads without consistently validating file types, and when uploaded content is stored in a directory served by the web server with script execution enabled.

Exploit preconditions

  • Attack surface: Authenticated back-office File Manager upload functionality - Required access: View-only back-office access sufficient to reach the affected endpoint - Trigger point: File upload processing through the multi() endpoint, including new filenames or chunked requests with a chunks parameter of 2 or higher - Why exploitation is possible: Inconsistent extension validation may allow executable server-side content to be stored in a web-accessible directory

Why this happens

The underlying issue is incomplete server-side validation of uploaded filenames and content across multiple upload code paths. When validation is skipped or applied inconsistently for new files or chunked uploads, an attacker-controlled file may be accepted and stored under a web-accessible path. This behavior maps to CWE-434, Unrestricted Upload of File with Dangerous Type, because the application does not reliably constrain uploads to non-executable content.

Potential impact

  • An attacker may execute arbitrary server-side code
  • The application or underlying host could be compromised
  • Sensitive application data may be accessed or modified
  • Uploaded content could be used to alter site behavior or distribute malware
  • The compromise may enable further movement within connected systems

General mitigation guidance

Mitigation generally focuses on treating uploaded files as untrusted data and ensuring every upload path applies the same controls. Common defensive patterns include allowlisting required file types based on verified content rather than trusting extensions, normalizing and safely generating stored filenames, and storing uploads outside the web root or serving them through a non-executable content handler. Secure-by-default configurations should disable script execution in upload directories, restrict upload permissions, limit file size and request resources, and run the application with only the privileges it requires. Chunked and alternate upload flows should share centralized validation and authorization checks.

How teams detect issues like this

Detection can include static analysis for upload handlers that trust filename extensions, write files directly beneath web roots, or apply validation only to selected request paths. Code reviews should examine multipart and chunked upload logic, filename generation, content-type handling, and web-server execution settings. Runtime monitoring can alert on executable extensions, unexpected scripts, or newly created files in upload directories. Policy enforcement may require centralized upload validation and prohibit executable content in user-controlled storage; automated code review tools can help flag inconsistent validation patterns.

Sources

SourceLink
github.comgithub.com/nivocart/nivocart
github.comgithub.com/nivocart/nivocart/blob/6ea6600cda1263ae70c0aab0a70d31091a32c46b/upload/admin/controller/common/filemanager.php#L527-L562
github.comgithub.com/nivocart/nivocart/blob/6ea6600cda1263ae70c0aab0a70d31091a32c46b/upload/admin/controller/common/filemanager_full.php
github.comgithub.com/nivocart/nivocart/issues/25
vulncheck.comvulncheck.com/advisories/nivocart-through-2.4.0-arbitrary-file-upload-rce-via-filemanager

Frequently asked

questions

It may be exploitable through the NivoCart back-office web interface when an attacker can authenticate with the required view-only access and reach the affected upload functionality.

Full administrative privileges may not be necessary. The described issue indicates that view-only back-office access can be sufficient, subject to deployment-specific authorization controls.

Apply centralized, server-side allowlist validation to every upload path, verify file content, store files outside executable web directories, and disable script execution wherever uploaded content is served.

Test normal, new-file, and chunked upload flows consistently; enforce least privilege; monitor upload directories; and add static or policy-based checks that reject executable content in user-controlled storage.

Find out what's already
exploitable in your codebase.