CVE-2024-38529
Admidio ≤ 4.3.10
Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2024-38529 is a critical-severity Unrestricted Upload of File with Dangerous Type (CWE-434) vulnerability in Admidio Admidio. Its CVSS base score is 9.0 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 33% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to SI-3 (Malicious Code Protection) and CM-7 (Least Functionality) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
Admidio is a free open-source user management system for organizations and groups. CVE-2024-38529 is an unrestricted file upload vulnerability (CWE-434) in the Message module of versions prior to 4.3.10. The flaw allows an authenticated user to upload a PHP file as a message attachment without any server-side extension validation; the file is then stored under the publicly reachable path adm_my_files/messages_attachments/ and can be executed by requesting its URL.
An attacker with a low-privileged account can therefore upload a web shell, achieve remote code execution on the server, and obtain full control over the application and its data. The CVSS 9.0 vector reflects network attack reachability, low complexity, required user interaction for the upload step, and changed scope that impacts the entire host.
The official GitHub Security Advisory GHSA-g872-jwwr-vggm and the accompanying patch (commit 3b1cc1c) state that the issue is resolved in Admidio 4.3.10 by adding proper file-type checks and preventing direct execution of uploaded attachments. Administrators should upgrade immediately and verify that the messages_attachments directory does not contain unexpected executable files.
EPSS for the CVE rose from a low baseline to a recorded peak of 0.0761 before receding to the current value of 0.0422, indicating a measurable but transient increase in exploitation interest after disclosure. No confirmed in-the-wild campaigns have been reported in the supplied references.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-2344
Vulnerability Data
Admidio is a free, open source user management system for websites of organizations and groups. In Admidio before version 4.3.10, there is a Remote Code Execution Vulnerability in the Message module of the Admidio Application, where it is possible to…
more
upload a PHP file in the attachment. The uploaded file can be accessed publicly through the URL `{admidio_base_url}/adm_my_files/messages_attachments/{file_name}`. The vulnerability is caused due to the lack of file extension verification, allowing malicious files to be uploaded to the server and public availability of the uploaded file. This vulnerability is fixed in 4.3.10.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V5.1.1
Mitigating Controls (NIST 800-53 r5) AI
Malicious-code protection at entry points blocks dangerous file types from being accepted and executed.
Least functionality restricts the file types and automatic processing capabilities the system will accept.
Mobile-code controls define, authorize, and block unacceptable uploaded code before automatic processing occurs.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Restricting execution of unauthorized software directly blocks dangerous uploaded files from running.
Hardened configuration baselines can enforce allowed file types and processing rules.
Secure development practices include input validation and file-type restrictions that prevent this weakness.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Configuration and acceptance testing verify that file-upload handling enforces allowed types and does not permit dangerous content to be stored or executed.
Secure-coding guidelines and security testing explicitly address restrictions on allowed file types and upload handling, reducing the risk that dangerous file uploads are accepted without validation.
Mandated testing for malicious content and known vulnerabilities reduces the likelihood that an outsourced component will contain or accept dangerous file types that could later be uploaded or executed.
Application allow-listing and pre-use scanning of received files directly blocks the introduction of executable content that has not been vetted, eliminating the primary vector for unrestricted dangerous file uploads.