Skip to main content
VulnerabilityPublished Updated

CVE-2024-23059: TOTOLINK A3300R · OS Command Injection

Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
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:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Jan 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

Immediate mitigation steps include isolating affected devices from untrusted networks and disabling remote management interfaces if enabled. Network administrators should monitor network traffic for unusual activity indicative of exploitation attempts. Employing network segmentation can limit the impact of a compromised router. Additionally, implementing strict access controls and using VPNs with strong authentication can reduce exposure. Regularly auditing router configurations and firmware versions across the network is essential. Organizations should also subscribe to vendor advisories and CVE databases to apply patches promptly once released. For critical environments, deploying intrusion detection systems (IDS) capable of detecting command injection patterns may provide early warning of exploitation attempts.

Description

TOTOLINK A3300R V17.0.0cu.557_B20221024 was discovered to contain a command injection vulnerability via the username parameter in the setDdnsCfg function.

References

Community reviews

Loading reviews…