# CVE-2020-9377: D-Link DIR-610 Devices Remote Command Execution

> Attackers can execute arbitrary commands remotely on unsupported D-Link DIR-610 routers via the command.php script.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 25 Mar 2022 (CISA KEV)
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Jul 2020
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-mvq3-fgc2-44m7

## What is CVE-2020-9377?

CVE-2020-9377 is a high-severity command injection vulnerability in n/a, published on 9 Jul 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

D-Link DIR-610 devices allow Remote Command Execution via the cmd parameter to command.php. NOTE: This vulnerability only affects products that are no longer supported by the maintainer

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

## Which versions are affected by CVE-2020-9377?

It affects 1 product.


Products: Dlink Dir-610 Firmware.

## How do I fix CVE-2020-9377?

No fix has been published for CVE-2020-9377 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 15 Apr 2022.

## Is CVE-2020-9377 being exploited?

Yes. Attackers have exploited CVE-2020-9377 in the wild since at least 25 Mar 2022.

## Other vulnerabilities in n/a

- [CVE-2020-9376](https://insights.sbomify.com/CVE-2020-9376/): Information disclosure in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-9377 and fix it if it is affected.

What it is: CVE-2020-9377 is a high-severity command injection vulnerability in n/a, published on 9 Jul 2020. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2020-9377 in the wild since at least 25 Mar 2022.

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-2020-9377/ (Markdown: https://insights.sbomify.com/CVE-2020-9377/index.md)
```

## Sources

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

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