CVE-2024-51115: DCME-320 · Command Injection
Affects DCME-320Source CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 10:12 UTC
- EPSS
- 1.7% chance of exploitation in 30 days – higher than 77% 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 5 Nov 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
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubclan-nad/DCME-320pkg:github/clan-nad/DCME-320Other threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Until an official patch is released, organizations should implement the following specific mitigations: 1) Restrict network access to DCME-320 systems by applying strict firewall rules and network segmentation to limit exposure to trusted hosts only. 2) Monitor logs and network traffic for unusual command execution patterns or unexpected outbound connections indicative of exploitation attempts. 3) Employ application-layer filtering or Web Application Firewalls (WAFs) that can detect and block command injection payloads targeting DCME-320. 4) Disable or restrict any unnecessary services or features within DCME-320 that could be exploited. 5) Conduct thorough input validation and sanitization on any interfaces interacting with DCME-320 if customization is possible. 6) Prepare for rapid patch deployment by maintaining close contact with the vendor for updates. 7) Implement endpoint detection and response (EDR) solutions to detect post-exploitation activities. 8) Educate IT and security teams about the vulnerability to ensure rapid incident response. These targeted actions go beyond generic advice by focusing on reducing attack surface and improving detection specific to command injection risks in DCME-320.
Description
DCME-320 v7.4.12.90 was discovered to contain a command injection vulnerability.