Skip to main content
VulnerabilityPublished Updated

CVE-2024-22529: TOTOLINK X2000R_V2 · 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 25 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

  1. Immediate Network Segmentation: Isolate affected TOTOLINK X2000R_V2 devices from critical internal networks to limit potential lateral movement if compromised.
  2. Disable Remote Management: If remote management features are enabled on the router, disable them to reduce exposure to external attackers.
  3. Monitor Network Traffic: Implement enhanced monitoring for unusual outbound connections or command execution patterns originating from these devices.
  4. Apply Firmware Updates: Continuously check for official firmware updates or security advisories from TOTOLINK and apply patches promptly once available.
  5. Temporary Device Replacement: Where feasible, replace vulnerable devices with models from vendors with active security support.
  6. Implement Intrusion Prevention Systems (IPS): Deploy IPS solutions capable of detecting command injection attempts targeting the boa web server or similar attack signatures.
  7. Harden Device Configuration: Change default credentials, disable unnecessary services, and enforce strong authentication mechanisms on management interfaces.
  8. Incident Response Preparedness: Prepare for potential compromise by having incident response plans tailored to router-level breaches, including device reimaging and network forensics.

Description

TOTOLINK X2000R_V2 V2.0.0-B20230727.10434 has a command injection vulnerability in the sub_449040 (handle function of formUploadFile) of /bin/boa.

References

Community reviews

Loading reviews…