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

> Attackers can execute arbitrary commands on TOTOLINK A810R routers via the downloadFile.cgi component.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Aug 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-q686-qg49-f6hm

## What is CVE-2022-38511?

CVE-2022-38511 is a high-severity command injection vulnerability in n/a, published on 28 Aug 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

TOTOLINK A810R V5.9c.4050_B20190424 was discovered to contain a command injection vulnerability via the component downloadFile.cgi.

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

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

It affects 1 product.


Products: Totolink A810r Firmware.

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

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

## Is CVE-2022-38511 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-28024](https://insights.sbomify.com/CVE-2025-28024/): Memory corruption in n/a (critical 9.8)
- [CVE-2025-28037](https://insights.sbomify.com/CVE-2025-28037/): Command injection in n/a (critical 9.8)
- [CVE-2025-28137](https://insights.sbomify.com/CVE-2025-28137/): Command injection in n/a (critical 9.8)
- [CVE-2022-25079](https://insights.sbomify.com/CVE-2022-25079/): Command injection in n/a (critical 9.8)
- [CVE-2025-28030](https://insights.sbomify.com/CVE-2025-28030/): Memory corruption in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-38511 is a high-severity command injection vulnerability in n/a, published on 28 Aug 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-38511 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-38511/ (Markdown: https://insights.sbomify.com/CVE-2022-38511/index.md)
```

## Sources

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

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