# CVE-2021-46007: Command injection in n/a

> An attacker can execute arbitrary OS commands on the TOTOLink A3100R router via the ping feature due to insufficient input filtering.

- **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:** 30 Mar 2022
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-m9r6-6whx-5pgr

## What is CVE-2021-46007?

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

### Official description

totolink a3100r V5.9c.4577 is vulnerable to os command injection. The backend of a page is executing the "ping" command, and the input field does not adequately filter special symbols. This can lead to command injection attacks.

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

## Which versions are affected by CVE-2021-46007?

It affects 1 product.


Products: Totolink Ar3100r Firmware.

## How do I fix CVE-2021-46007?

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

## Is CVE-2021-46007 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-46007 and fix it if it is affected.

What it is: CVE-2021-46007 is a critical command injection vulnerability in n/a, published on 30 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-2021-46007 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-2021-46007/ (Markdown: https://insights.sbomify.com/CVE-2021-46007/index.md)
```

## Sources

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

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