# CVE-2026-105484: TOTOLINK X6000R UploadFirmwareFile cstecgi.cgi firmware_check os command injection

> Remote attackers can execute arbitrary OS commands on TOTOLINK X6000R routers via the firmware upload handler.

- **Severity:** Critical 10.0 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Oct 2026
- **Updated:** 6 Oct 2026
- **Also known as:** GHSA-34j5-jp28-25g9

## What is CVE-2026-105484?

CVE-2026-105484 is a critical command injection vulnerability in TOTOLINK X6000R, published on 6 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A security vulnerability has been detected in TOTOLINK X6000R 9.4.0cu.652_B20230116. The impacted element is the function firmware_check of the file /cgi-bin/cstecgi.cgi of the component UploadFirmwareFile Handler. Such manipulation of the argument file_name leads to os command injection. The attack may be performed from remote.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command), CWE-77 (Improper Neutralization of Special Elements used in a Command)

## Which versions are affected by CVE-2026-105484?


## How do I fix CVE-2026-105484?

No fix has been published for CVE-2026-105484 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-105484 being exploited?

There is no known exploitation of CVE-2026-105484 in the wild and no public exploit code.

Public exploit code:

- Research attribution and coordinated disclosure status for CVE-2026-105484. (github_poc): https://github.com/xiaobai718-ab/CVE-2026-105484

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-105484 and fix it if it is affected.

What it is: CVE-2026-105484 is a critical command injection vulnerability in TOTOLINK X6000R, published on 6 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-105484 in the wild and no public exploit code.

Affected product: TOTOLINK X6000R. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-105484/ (Markdown: https://insights.sbomify.com/CVE-2026-105484/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-105484
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-105484
- OSV: https://osv.dev/vulnerability/CVE-2026-105484

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-105484/
Summaries are generated and may contain mistakes; the official description above is the record.