# CVE-2022-26209: Command injection in n/a

> Attackers can execute arbitrary commands on Totolink routers via a crafted request to the setUploadSetting function.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Mar 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-2563-r73r-7cq9

## What is CVE-2022-26209?

CVE-2022-26209 is a critical command injection vulnerability in n/a, published on 15 Mar 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Totolink A830R V5.9c.4729_B20191112, A3100R V4.1.2cu.5050_B20200504, A950RG V4.1.2cu.5161_B20200903, A800R V4.1.2cu.5137_B20200730, A3000RU V5.9c.5185_B20201128, and A810R V4.1.2cu.5182_B20201026 were discovered to contain a command injection vulnerability in the function setUploadSetting, via the FileName parameter. This vulnerability allows attackers to execute arbitrary commands via a crafted request.

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

## Which versions are affected by CVE-2022-26209?

It affects 6 products.


Products: Totolink A3000ru Firmware, Totolink A3100r Firmware, Totolink A800r Firmware, Totolink A810r Firmware, Totolink A830r Firmware, Totolink A950rg Firmware.

## How do I fix CVE-2022-26209?

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

## Is CVE-2022-26209 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-28034](https://insights.sbomify.com/CVE-2025-28034/): Command injection in n/a (critical 9.8)
- [CVE-2025-28035](https://insights.sbomify.com/CVE-2025-28035/): Command injection in n/a (critical 9.8)
- [CVE-2025-28036](https://insights.sbomify.com/CVE-2025-28036/): Command injection in n/a (critical 9.8)
- [CVE-2022-26206](https://insights.sbomify.com/CVE-2022-26206/): Command injection in n/a (critical 9.8)
- [CVE-2022-26207](https://insights.sbomify.com/CVE-2022-26207/): Command injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-26209 and fix it if it is affected.

What it is: CVE-2022-26209 is a critical command injection vulnerability in n/a, published on 15 Mar 2022. 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-2022-26209 in the wild and no public exploit code.

Affected product: n/a. 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-2022-26209/ (Markdown: https://insights.sbomify.com/CVE-2022-26209/index.md)
```

## Sources

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

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