X6000r Firmware vulnerabilitiesRanked by how likely they are to be used.
X6000r Firmware is made by Totolink. We track 54 published vulnerabilities in it, across 4 versions. None of them is on the list of flaws known to be exploited today. If you run X6000r Firmware, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which X6000r Firmware vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of X6000r Firmware's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which X6000r Firmware flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 15%CVE-2024-1781Medium
A vulnerability was found in Totolink X6000R AX3000 9.4.0cu.852_20230719.
- 13%CVE-2025-52906Critical
Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') vulnerability in TOTOLINK X6000R allows OS Command Injection.This issue affects X6000R: through V9.4.0cu.1360_B20241207.
- 8.4%CVE-2025-52905High
Improper Input Validation vulnerability in TOTOLINK X6000R allows Flooding.This issue affects X6000R: through V9.4.0cu.1360_B20241207.
- 6.2%CVE-2024-7907Medium
A vulnerability, which was classified as critical, has been found in TOTOLINK X6000R 9.4.0cu.852_20230719.
- 4.0%CVE-2024-2353High
A vulnerability, which was classified as critical, has been found in Totolink X6000R 9.4.0cu.852_20230719.
- 2.8%CVE-2023-50651Critical
TOTOLINK X6000R v9.4.0cu.852_B20230719 was discovered to contain a remote command execution (RCE) vulnerability via the component /cgi-bin/cstecgi.cgi.
- 2.3%CVE-2025-52284Medium
Totolink X6000R V9.4.0cu.1360_B20241207 was found to contain a command injection vulnerability in the sub_4184C0 function via the tz parameter.
- 1.9%CVE-2023-46418Critical
TOTOLINK X6000R v9.4.0cu.652_B20230116 was discovered to contain a remote command execution (RCE) vulnerability via the sub_412688 function.
- 1.9%CVE-2023-46419Critical
TOTOLINK X6000R v9.4.0cu.652_B20230116 was discovered to contain a remote command execution (RCE) vulnerability via the sub_415730 function.
- 1.9%CVE-2023-46422Critical
TOTOLINK X6000R v9.4.0cu.652_B20230116 was discovered to contain a remote command execution (RCE) vulnerability via the sub_411994 function.
Running X6000r Firmware? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
A vulnerability was found in Totolink X6000R AX3000 9.4.0cu.852_20230719. It has been rated as critical. This issue affects the function setWizardCfg of the file /cgi-bin/cstecgi.cgi of the component shttpd. The manipulation leads to command injection. The exploit has been disclosed to the public and may be used. The identifier VDB-254573 was assigned to this vulnerability. NOTE: The vendor was contacted early about this disclosure but did not respond in any way.
- Matched to
- X6000r Firmware on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 54 published vulnerabilities listed under the name X6000r Firmware, across 4 versions.
None of X6000r Firmware's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track X6000r Firmware. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.