CVE-2024-48659: Command Injection
Source CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 1.1% chance of exploitation in 30 days – higher than 66% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 21 Oct 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
AI-suggested
Given the absence of official patches, organizations should immediately implement network-level protections such as firewall rules to restrict access to the log_u_umount.php component, limiting exposure to trusted IP addresses only. Employ intrusion detection and prevention systems (IDS/IPS) with signatures or heuristics targeting command injection attempts on this endpoint. Conduct thorough logging and monitoring for unusual command execution or web requests targeting the vulnerable component. Segmentation of critical systems running DCME-320-L can reduce lateral movement risk if exploitation occurs. Disable or restrict the log_u_umount.php functionality if feasible until a patch is released. Engage with the vendor for updates and apply patches promptly once available. Additionally, conduct vulnerability scanning and penetration testing focused on this component to identify potential exploitation attempts. Educate security teams about this vulnerability to ensure rapid incident response if exploitation is detected.
Description
An issue in DCME-320-L <=9.3.2.114 allows a remote attacker to execute arbitrary code via the log_u_umount.php component.