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

> A local attacker can execute arbitrary code on D-Link 5G CPE devices by sending a crafted payload to the Diagnostics function.

- **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:** 12 Nov 2024
- **Updated:** 13 Nov 2024
- **Also known as:** GHSA-j6wf-wwwg-83hx

## What is CVE-2024-28726?

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

### Official description

An issue in DLink DWR 2000M 5G CPE With Wifi 6 Ax1800 and Dlink DWR 5G CPE DWR-2000M_1.34ME allows a local attacker to execute arbitrary code via a crafted payload to the Diagnostics function.

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

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


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

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

## Is CVE-2024-28726 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-28726 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2024-28726 is a high-severity command injection vulnerability in n/a, published on 12 Nov 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-28726 exists.

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

## Sources

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

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