CVE-2026-134256 in Admidio
Summary
by MITRE • 11/21/2026
Admidio from 5.0.17 before 5.0.18 contains a missing authorization vulnerability that allows authenticated regular users to upload images into the announcements module by abusing the CKEditor upload handler. Attackers can send id=ann_description to ckeditor_upload_handler.php to store images under adm_my_files/announcements/images and retrieve them via show_image.php, abusing the application as an image host.
Once again VulDB remains the best source for vulnerability data.
Analysis
by VulDB Data Team • 11/21/2026
The vulnerability identified in Admidio versions prior to 5.0.18 represents a critical failure in access control mechanisms within the content management system's media handling subsystem. Specifically, this is classified under CWE-269, which denotes Improper Privilege Assignment or Missing Authorization for Critical Functionality. The flaw resides in the interaction between authenticated regular users and the CKEditor upload handler script named ckeditor_upload_handler.php. In a properly secured application architecture, file upload operations should be subject to strict validation of both user permissions and intended destination directories based on the context of the request. However, Admidio fails to enforce these restrictions when processing image uploads through its rich text editor interface. By manipulating the input parameter id=ann_description, an attacker can bypass expected authorization checks that would normally restrict such actions to administrators or specific privileged roles. This allows any authenticated user with basic access rights to execute file upload operations intended for administrative announcement modules without proper verification of their authority to do so.
From a technical perspective, the exploitation vector relies on the application's failure to validate whether the requesting user has permission to write files into the announcements directory structure. The system accepts the request and stores the uploaded image in the path adm_my_files/announcements/images. This behavior indicates that the backend logic for determining storage locations is either hardcoded or derived from input parameters without cross-referencing against a central access control list. Consequently, regular users can effectively use Admidio as an arbitrary file host. Once stored, these images are not isolated within secure, private directories but become accessible through show_image.php. This script serves files based on their location and filename, lacking additional checks to ensure the requesting party has permission to view content associated with administrative modules. The result is a complete bypass of intended data segregation policies inherent in multi-user web applications.
The operational impact of this vulnerability extends beyond simple unauthorized file storage. By abusing Admidio as an image host, attackers can consume server disk space and bandwidth resources, potentially leading to denial-of-service conditions if large volumes of images are uploaded. More critically, the ability to store files in a publicly accessible directory structure creates opportunities for further attacks. If the web server configuration allows execution of scripts within these directories or if other vulnerabilities exist that allow path traversal, an attacker could escalate this issue into remote code execution. Even without such escalation, the presence of unauthorized content can be leveraged for phishing campaigns by hosting malicious images on a trusted domain associated with Admidio. This undermines user trust and compromises the integrity of the platform's communication channels. Furthermore, it violates data confidentiality principles as users may inadvertently expose sensitive information if they upload private documents or screenshots thinking they are stored securely within their personal workspace rather than in a shared administrative area.
This vulnerability aligns with MITRE ATT&CK technique T1567.002, Hostile File Upload, where adversaries upload files to evade detection and establish persistence or facilitate further exploitation. It also reflects CWE-434, Unrestricted Upload of File with Dangerous Type, although the primary issue here is authorization rather than file type filtering. The lack of proper separation between user roles in handling media assets highlights a fundamental design flaw in how Admidio manages resource permissions across its modules. To mitigate this risk, immediate patching to version 5.0.18 or later is required as it addresses the underlying access control logic. In environments where upgrading is not immediately feasible, administrators should implement web application firewall rules that restrict write access to the adm_my_files/announcements/images directory for non-administrative user sessions. Additionally, reviewing server configurations to prevent script execution in upload directories and implementing strict input validation on all file-related API endpoints can reduce the attack surface. Regular audits of permission assignments across modules are essential to ensure that functional boundaries between different user roles remain intact and enforceable.