CVE-2026-134259 in Admidioinfo

Summary

by MITRE • 11/21/2026

Admidio from 5.0.16 before 5.0.18 contains a stored cross-site scripting vulnerability that allows users with folder upload rights to store JavaScript by uploading SVG files served inline. Attackers can upload a script-bearing SVG that downloadFile() serves as image/svg+xml inline without nosniff or CSP, executing on the Admidio origin for viewers including unauthenticated visitors.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Analysis

by VulDB Data Team • 11/21/2026

The vulnerability identified in Admidio versions prior to 5.0.18 represents a critical stored cross-site scripting flaw rooted in improper validation of file uploads and subsequent content type handling. This security defect specifically targets users who possess folder upload privileges, allowing them to bypass standard input sanitization by embedding malicious JavaScript payloads within SVG files. The core technical failure lies in the application's decision to serve these uploaded SVG files inline as image/svg+xml without implementing strict Content Security Policy headers or enforcing a nosniff directive. Consequently, when an administrator or any other user views the affected page containing the malicious file reference, the browser interprets and executes the embedded script within the context of the Admidio origin rather than treating it as static data.

From a technical perspective, this vulnerability exploits the lack of strict MIME type sniffing prevention mechanisms in the web server configuration for specific endpoints handling user-uploaded content. By uploading an SVG file containing executable JavaScript code, an attacker can persistently store malicious scripts on the server side. Unlike reflected XSS where the payload is delivered via a link, stored XSS ensures that every visitor to the compromised page triggers the execution of the script. The absence of Content Security Policy directives means there are no restrictions preventing inline script execution or unauthorized external resource loading, which further exacerbates the severity of the issue by allowing complex attack chains such as session hijacking or credential theft through keylogging scripts embedded in the SVG payload.

The operational impact of this vulnerability is severe due to its potential for widespread exploitation among unauthenticated visitors and authenticated users alike. An attacker can leverage this flaw to steal sensitive user data, including session cookies, authentication tokens, and personally identifiable information stored within the application's database or local storage. Furthermore, because the script executes on the Admidio origin, it possesses full access to all functionalities available to a logged-in user of that role level. This capability enables attackers to perform actions such as modifying configuration settings, creating new administrative accounts, deleting records, or exfiltrating entire datasets from the application's backend systems without detection by standard security monitoring tools that do not inspect DOM-based activities.

This vulnerability aligns with CWE-79, which classifies improper neutralization of input during web page generation known as cross-site scripting. Additionally, it maps to MITRE ATT&CK technique T1059, specifically the command and script interpretation subcategory, where attackers use scripts like JavaScript or VBScript to execute malicious commands on a victim's system. The persistence aspect also relates to CWE-643, which describes improper mitigation of XSS in HTML applications by failing to neutralize special characters before inclusion in output. These classifications highlight the fundamental failure in input validation and output encoding practices that characterize this security defect within the Admidio platform architecture.

To mitigate this vulnerability, administrators must immediately upgrade Admidio to version 5.0.18 or later where these issues have been addressed through enhanced file upload filtering and stricter content type enforcement. In environments where upgrading is not immediately feasible, implementing a robust Content Security Policy that explicitly disallows inline scripts can significantly reduce the impact of such attacks by preventing the execution of malicious JavaScript embedded in SVG files. Additionally, configuring web servers to enforce strict MIME type checking using X-Content-Type-Options: nosniff headers ensures that browsers do not sniff content types and instead adhere strictly to declared MIME types, thereby preventing the browser from interpreting an uploaded file as executable script if it is mislabeled or contains embedded code. Input validation should also be strengthened to reject SVG files containing any JavaScript elements such as script tags or event handlers before they are stored on the server filesystem.

Responsible

VulnCheck

Reservation

11/21/2026

Disclosure

11/21/2026

Moderation

accepted

CPE

ready

EPSS

0.00000

KEV

no

Activities

very low

Sources

Want to stay up to date on a daily basis?

Enable the mail alert feature now!