CVE-2024-24326: n/a
Source CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 1.6% chance of exploitation in 30 days – higher than 76% 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 30 Jan 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 2026-10-26.
What to do
AI-suggested
Until an official patch is released, organizations should implement the following mitigations: 1) Immediately isolate affected TOTOLINK A3300R devices from untrusted networks, especially the internet, to reduce exposure. 2) Disable remote management interfaces and services on the router to prevent external access to vulnerable functions. 3) Employ network segmentation to limit the router's access to critical internal resources. 4) Monitor network traffic for unusual patterns or command injection attempts targeting the arpEnable parameter or DHCP configurations. 5) Replace affected devices with alternative hardware from vendors with timely security updates if possible. 6) Regularly check for firmware updates from TOTOLINK and apply patches as soon as they become available. 7) Educate network administrators about this vulnerability and enforce strict access controls on network devices. These steps go beyond generic advice by focusing on immediate containment, monitoring, and proactive device management.
Description
TOTOLINK A3300R V17.0.0cu.557_B20221024 was discovered to contain a command injection vulnerability via the arpEnable parameter in the setStaticDhcpRules function.