Skip to main content
CVE-2024-31807VulnerabilityPublished Updated

CVE-2024-31807: n/a

Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.3% chance of exploitation in 30 days – higher than 71% 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 8 Apr 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 2026-10-26.

What to do

AI-suggested

Organizations should immediately implement network-level mitigations to reduce exposure. These include disabling remote management interfaces on TOTOLINK EX200 routers, restricting access to the device management ports via firewall rules, and segmenting the network to isolate vulnerable devices from critical infrastructure. Monitoring network traffic for unusual NTP synchronization requests or unexpected activity from the router can help detect exploitation attempts. Until an official patch is released, consider replacing affected devices with alternative hardware or firmware versions not impacted by this vulnerability. Vendors and users should prioritize firmware updates once available. Additionally, applying strict input validation and employing network intrusion detection systems tuned to detect exploitation patterns can further reduce risk.

Description

TOTOLINK EX200 V4.0.3c.7646_B20201211 was discovered to contain a remote code execution (RCE) vulnerability via the hostTime parameter in the NTPSyncWithHost function.

References

Community reviews

Loading reviews…