CVEReports
CVEReports

Automated vulnerability intelligence platform. Comprehensive reports for high-severity CVEs generated by AI.

Product

  • Home
  • Sitemap
  • RSS Feed

Company

  • About
  • Contact
  • Privacy Policy
  • Terms of Service

© 2026 CVEReports. All rights reserved.

Made with love by Amit Schendel & Alon Barad



CVE-2026-104890

CVE-2026-104890: Remote Code Execution via Mixed-Case File Upload Bypass in Kunstmaan CMS MediaBundle

Amit Schendel
Amit Schendel
Senior Security Researcher

Oct 7, 2026·6 min read·23 visits

Executive Summary (TL;DR)

An authenticated administrator can bypass file upload restrictions by uploading mixed-case extensions (e.g., .pHp), which are subsequently normalized to .php and stored on the filesystem, enabling remote code execution.

Kunstmaan CMS MediaBundle prior to version 7.3.2 contains a critical file upload vulnerability where case-sensitive extension checks can be bypassed using mixed-case file extensions. Because extension normalization occurs after the validation routine, files with mixed-case executable extensions (such as pHp) bypass checks but are stored with normalized lowercase executable extensions, allowing authenticated administrators to achieve remote code execution.

Vulnerability Overview

The Kunstmaan CMS MediaBundle component provides file upload and media management capabilities for web applications built on the Symfony framework. The vulnerability, tracked as CVE-2026-104890, resides within the file path generation and extension checking routines of this component. Specifically, the system employs a case-sensitive file extension blacklist that can be bypassed by uploading assets with mixed-case or uppercase extensions.

Because the CMS utilizes a default blacklist that covers only a narrow set of extensions, it fails to restrict multiple executable types. Furthermore, the component normalizes the extension to lowercase after executing the security check, leading to the storage of executable files on the disk. This order-of-operations discrepancy allows authenticated backend operators with media upload privileges to achieve remote code execution on the underlying hosting environment.

This security flaw represents a combination of unrestricted file upload with dangerous type (CWE-434) and loss of case sensitivity (CWE-178). It poses a significant risk to organizations where multiple administrative or editing roles exist, as any user with permission to upload media can execute arbitrary commands with the privileges of the web server process.

Root Cause Analysis

The root cause of CVE-2026-104890 lies in a logical flaw and temporal discrepancy during the validation and sanitization of user-supplied filenames. When a file is uploaded, the FileHandler::getFilePath method parses the original filename to determine its storage destination. To prevent malicious file uploads, the application matches the file extension against a configured array of blacklisted extensions using a regular expression.

The regular expression implementation, preg_replace('/\.(' . implode('|', $this->blacklistedExtensions) . ')$/', '.txt', $filename), lacks the case-insensitive modifier (i). Consequently, the blacklist match is strictly case-sensitive. An extension such as pHp or PHP does not match the default lowercase entry php in the blacklist array, and the input passes through the validation step unaltered.

Following the validation routine, the application extracts the file extension and normalizes it to lowercase via strtolower($parts['extension']) before appending it back to the filename for disk write operations. This design flaw performs normalization after the security check rather than before. As a result, the bypassed mixed-case file shell.pHp is normalized and persisted as shell.php on the web server filesystem.

Code Analysis

Analyzing the vulnerable implementation in FileHandler::getFilePath highlights how the sequence of operations introduces the security gap. In the unpatched codebase, the application processes the path as follows:

// Vulnerable Order of Operations
if (!empty($this->blacklistedExtensions)) {
    // Case-sensitive check fails to match mixed-case extensions
    $filename = preg_replace('/\.(' . implode('|', $this->blacklistedExtensions) . ')$/', '.txt', $filename);
}
 
$parts = pathinfo($filename);
$filename = $this->slugifier->slugify($parts['filename']);
if (\array_key_exists('extension', $parts)) {
    // Normalization occurs after the validation check has passed
    $filename .= '.' . strtolower($parts['extension']);
}

The official patch introduced in version 7.3.2 restructures this logic to perform case folding before any security decisions are executed. The updated code extracts the extension, converts it to lowercase, and then evaluates it against both the blacklist and a newly introduced whitelist:

// Patched Implementation
$parts = pathinfo($filename);
$basename = $this->slugifier->slugify($parts['filename']);
 
if (!\array_key_exists('extension', $parts)) {
    return sprintf('%s/%s', $media->getUuid(), $basename);
}
 
// Normalize the extension to lowercase first
$extension = strtolower($parts['extension']);
 
// Validate the normalized extension
if (!$this->isAllowedExtension($extension)) {
    $extension = 'txt';
}

This change ensures that all extension checks occur on the normalized representation, preventing any case-sensitivity bypasses. Additionally, the helper method isAllowedExtension performs strict type comparisons against lowercase arrays of blacklisted and allowed extensions.

Exploitation Methodology

Exploitation of CVE-2026-104890 requires the attacker to hold an authenticated account with media management or upload privileges. The attack is highly reliable due to the deterministic nature of the filename normalization logic. The process begins with the preparation of a script container containing server-side code, such as PHP instructions designed to execute system commands.

The attacker names the payload file with a mixed-case extension such as payload.pHp to avoid matching the default case-sensitive blacklist entry php. Upon uploading the file to the media asset manager, the application accepts the file without altering its extension to .txt. The system then lowercases the extension and saves the file to the public upload directory.

To complete the execution cycle, the attacker requests the file directly through the web server. Because the files are stored within the web-accessible directory (/public/uploads/media/<uuid>/), and because standard web server configurations pass .php requests to a PHP interpreter, the script is executed by the server, allowing remote command execution.

Impact Assessment

The security impact of successful exploitation is critical, as it leads to execution of arbitrary operating system commands within the context of the web server daemon (e.g., www-data or nginx). Depending on the hosting configuration, an attacker can leverage this execution capability to perform local privilege escalation, compromise database credentials stored in environment variables, and access local system files.

The CVSS v3.1 score is calculated at 7.2 (High), reflecting network accessibility and low attack complexity, although tempered by the requirement for high privileges (PR:H). Despite the prerequisite of administrative or publisher-level authentication, the impact on confidentiality, integrity, and availability is maximum (C:H/I:H/A:H).

In containerized environments, the compromise may be restricted to the container instance, but it still exposes adjacent infrastructure via lateral network movement. On shared or poorly configured servers, this compromise can lead to complete host takeover, installation of persistent backdoors, or deployment of additional malicious payloads.

Remediation & Hardening Guidance

The primary remediation mechanism is the installation of Kunstmaan Bundles CMS version 7.3.2 or later. This upgrade addresses both the case-sensitivity loophole and expands the default blacklisted extensions array to cover related script types such as .phtml, .phar, and .php5. If immediate upgrade is not feasible, administrators must configure web server controls to block execution in upload directories.

For Nginx environments, script execution within the media directory can be disabled by adding a specific location block that denies execution of PHP assets within the media upload directory path. For Apache environments, administrators can disable script interpretation by placing a configuration directive that removes handlers for executable extensions in the target folder.

Furthermore, developers should define an explicit allowed-extensions whitelist in the CMS configuration. Defining a strict whitelist ensures that only expected, passive media types such as images, documents, and stylesheets are processed and saved, providing defense-in-depth against future bypass variants.

Technical Appendix

CVSS Score
7.2/ 10
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
EPSS Probability
0.42%
Top 66% most exploited

Affected Systems

Kunstmaan CMS MediaBundle

Affected Versions Detail

Product
Affected Versions
Fixed Version
MediaBundle
Kunstmaan
< 7.3.27.3.2
AttributeDetail
CWE IDCWE-434
Attack VectorNetwork (AV:N)
Attack ComplexityLow (AC:L)
Privileges RequiredHigh (PR:H)
CVSS Score7.2 (High)
Exploit StatusPoC Available
EPSS Score0.00416 (0.42%)

MITRE ATT&CK Mapping

T1059Command and Scripting Interpreter
Execution
T1105Ingress Tool Transfer
Command and Control
CWE-434
Unrestricted Upload of File with Dangerous Type

The product allows the attacker to upload or transfer files of dangerous types that can be automatically processed within the product's environment.

Vulnerability Timeline

Security patch committed to repository
2026-09-04
Security release 7.3.2 published
2026-10-05
GHSA-p279-5wcv-45vq advisory disclosed
2026-10-05
CVE-2026-104890 assigned and published
2026-10-05

Attack Flow Diagram

Press enter or space to select a node. You can then use the arrow keys to move the node around. Press delete to remove it and escape to cancel.
Press enter or space to select an edge. You can then press delete to remove it or escape to cancel.

More Reports

•about 17 hours ago•CVE-2026-58254
6.5

CVE-2026-58254: Authorization Bypass in NATS Server Message Tracing for Leaf Node Connections

NATS Server prior to versions 2.12.8 and 2.14.3 contains an incorrect authorization vulnerability (CWE-863) in its message tracing subsystem. When evaluating whether a connection is permitted to publish trace events to a destination subject specified in the Nats-Trace-Dest header, the server only checks standard client permissions and omits permission checks for leaf node connections. This allows a connected leaf node operator with restricted publishing privileges to emit internal trace events to unauthorized subjects and suppress standard message delivery using the Nats-Trace-Only header.

Alon Barad
Alon Barad
4 views•10 min read
•about 18 hours ago•CVE-2026-63341
7.5

CVE-2026-63341: Unauthenticated Denial of Service via Unbounded Topic Depth in Aedes MQTT Broker

CVE-2026-63341 is a high-severity Denial of Service (DoS) vulnerability in the Aedes MQTT broker for Node.js affecting all versions prior to 1.1.1. The flaw stems from missing input validation on the hierarchical depth of incoming MQTT topic strings before they are passed to the underlying topic-matching engine, qlobber. Because qlobber enforces a hardcoded limit of 100 topic levels and throws a synchronous exception when this threshold is exceeded, an attacker can send a single MQTT packet containing 101 or more forward-slash-separated levels to trigger an uncaught exception that immediately terminates the Node.js broker process.

Alon Barad
Alon Barad
5 views•12 min read
•about 19 hours ago•CVE-2026-61725
6.1

CVE-2026-61725: Path Traversal and Arbitrary File Overwrite in sevenz-rust2

CVE-2026-61725 is a path traversal vulnerability (CWE-22) in the sevenz-rust2 Cargo package prior to version 0.21.1. The vulnerability occurs because the decompression utility fails to validate or sanitize archive entry filenames before joining them with the destination directory path via std::path::Path::join. An attacker who supplies a crafted 7z archive containing parent directory traversal sequences or absolute paths can write or overwrite arbitrary files on the host filesystem with the privileges of the extracting process.

Alon Barad
Alon Barad
5 views•12 min read
•about 20 hours ago•CVE-2026-77309
8.8

CVE-2026-77309: Unauthenticated Remote Code Execution in NASA-AMMOS AIT-GUI via Incomplete File Cleanup and Path Traversal

CVE-2026-77309 (GHSA-jrjx-9jjw-747m) is a high-severity unauthenticated remote code execution vulnerability affecting NASA-AMMOS AIT-GUI versions 1.0.0 through 2.5.0. The flaw results from chaining an incomplete file cleanup error in the telemetry query endpoint (/tlm/query) with a directory traversal flaw in the script execution endpoint (/script/run). An attacker on an adjacent network can stage arbitrary Python statements into a static file on disk and execute that file under the privileges of the AIT-GUI web server process.

Amit Schendel
Amit Schendel
10 views•10 min read
•about 21 hours ago•CVE-2026-77332
2.3

CVE-2026-77332: Surfaced-Memory Envelope Injection and Stored Prompt Injection in memtomem-stm

A vulnerability classified under CWE-116 (Improper Encoding or Escaping of Output) exists in memtomem-stm versions 0.1.0 through 0.1.33. The software acts as a Model Context Protocol (MCP) short-term memory proxy gateway for AI agent architectures. When surfacing retrieved memories and scratchpad items into downstream Large Language Model (LLM) context envelopes, the SurfacingFormatter component fails to properly sanitize untrusted memory attributes. An attacker with the ability to plant untrusted content into the agent's long-term or working memory store can inject arbitrary structural delimiters, close the <surfaced-memories> XML boundary prematurely, visually obscure instructions using Unicode bidirectional overrides, and execute stored prompt injection attacks against downstream LLM agents.

Alon Barad
Alon Barad
12 views•10 min read
•about 22 hours ago•CVE-2026-77331
2.0

CVE-2026-77331: Race Condition and Session State Corruption in memtomem-stm

CVE-2026-77331 (GHSA-72jh-722p-rqr3) is a concurrency and session-state synchronization vulnerability in memtomem-stm, a short-term memory proxy gateway for AI agents. In versions 0.1.2 prior to 0.1.34, concurrent Model Context Protocol (MCP) Remote Procedure Call (RPC) failures or mid-flight task cancellations can initiate duplicate reconnect loops and permit dirty or cancelled transport sessions to be reused. This deficiency results in session-state integrity loss and local service degradation.

Amit Schendel
Amit Schendel
6 views•9 min read