# CVE-2025-7192: D-Link DIR-645 ssdpcgi cgibin ssdpcgi_main command injection

> Remote attackers can execute arbitrary commands on unsupported D-Link DIR-645 routers via the ssdpcgi_main function.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Jul 2025
- **Updated:** 9 Jul 2025
- **Also known as:** GHSA-w9ww-h3pr-mc4g

## What is CVE-2025-7192?

CVE-2025-7192 is a medium-severity command injection vulnerability in D-Link DIR-645, published on 8 Jul 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was found in D-Link DIR-645 up to 1.05B01 and classified as critical. This issue affects the function ssdpcgi_main of the file /htdocs/cgibin of the component ssdpcgi. The manipulation leads to command injection. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. This vulnerability only affects products that are no longer supported by the maintainer.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command), CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

## Which versions are affected by CVE-2025-7192?

It affects 1 product.


Products: Dlink Dir-645 Firmware.

## How do I fix CVE-2025-7192?

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

## Is CVE-2025-7192 being exploited?

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

## Other vulnerabilities in D-Link DIR-645

- [CVE-2015-2051](https://insights.sbomify.com/CVE-2015-2051/): D-Link DIR-645 Router Remote Code Execution (high 8.8, exploited in the wild)
- [CVE-2015-2052](https://insights.sbomify.com/CVE-2015-2052/): Memory corruption in n/a (critical 10.0)
- [CVE-2023-36089](https://insights.sbomify.com/CVE-2023-36089/): Auth bypass in n/a (critical 9.8)
- [CVE-2022-46475](https://insights.sbomify.com/CVE-2022-46475/): Memory corruption in n/a (critical 9.8)
- [CVE-2022-32092](https://insights.sbomify.com/CVE-2022-32092/): Command injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-7192 and fix it if it is affected.

What it is: CVE-2025-7192 is a medium-severity command injection vulnerability in D-Link DIR-645, published on 8 Jul 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-7192 exists.

Affected product: D-Link DIR-645. 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-2025-7192/ (Markdown: https://insights.sbomify.com/CVE-2025-7192/index.md)
```

## Sources

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

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