CVE-2024-57695: Command Injection
Source CVE Database V5
Not known to be exploited · CVSS 7.7 High.
Data as of 26 Oct 2026, 09:08 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 11 Nov 2025
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
The primary mitigation is to upgrade all instances of Agnitum Outpost Security Suite to version 8.0 or later, which contains the fix for this vulnerability. Organizations should conduct an inventory to identify any systems still running versions 7.5.3 or 7.6 and prioritize their upgrade. In environments where upgrading is not immediately feasible, restrict local access to trusted personnel only and implement strict endpoint access controls and monitoring to detect suspicious activities. Employ application whitelisting and behavior-based endpoint detection to identify attempts to exploit the lock function. Regularly audit and harden local user permissions to minimize the risk of unauthorized local code execution. Additionally, educate staff about the risks of local attacks and enforce policies to prevent unauthorized physical or remote local access. Finally, maintain up-to-date threat intelligence feeds to monitor for any emerging exploit attempts targeting this vulnerability.
Description
An issue in Agnitum Outpost Security Suite 7.5.3 (3942.608.1810) and 7.6 (3984.693.1842) allows a local attacker to execute arbitrary code via the lock function. The manufacturer fixed the vulnerability in version 8.0 (4164.652.1856) from December 17, 2012.