# CVE-2024-51151: Command injection in n/a

> Remote attackers can execute arbitrary commands on D-Link DI-8200 routers via the msp_info_htm function parameters.

- **Severity:** High 8.0 (`CVSS:3.1/AV:A/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:** 20 Nov 2024
- **Updated:** 22 Nov 2024
- **Also known as:** GHSA-jrww-p4wq-2pxx

## What is CVE-2024-51151?

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

### Official description

D-Link DI-8200 16.07.26A1 is vulnerable to remote command execution in the msp_info_htm function via the flag parameter and cmd parameter.

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

## Which versions are affected by CVE-2024-51151?

It affects 1 product.


Products: Dlink Di-8200 Firmware.

## How do I fix CVE-2024-51151?

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

## Is CVE-2024-51151 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-51383](https://insights.sbomify.com/CVE-2025-51383/): Memory corruption in n/a (low 3.5)
- [CVE-2025-51384](https://insights.sbomify.com/CVE-2025-51384/): Memory corruption in n/a (low 3.5)
- [CVE-2025-51385](https://insights.sbomify.com/CVE-2025-51385/): Memory corruption in n/a (low 3.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-51151 and fix it if it is affected.

What it is: CVE-2024-51151 is a high-severity command injection vulnerability in n/a, published on 20 Nov 2024. 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-2024-51151 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-2024-51151/ (Markdown: https://insights.sbomify.com/CVE-2024-51151/index.md)
```

## Sources

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

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