# CVE-2025-60700: Command injection in n/a

> Unauthenticated remote attackers can execute arbitrary commands on D-Link DIR-882 routers via unsanitized input in the web interface.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Nov 2025
- **Updated:** 14 Nov 2025
- **Also known as:** GHSA-3r52-h47w-2p2j

## What is CVE-2025-60700?

CVE-2025-60700 is a medium-severity command injection vulnerability in n/a, published on 13 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A command injection vulnerability exists in the D-Link DIR-882 Router firmware DIR882A1_FW102B02 within the `prog.cgi` and `librcm.so` binaries. The `sub_4455BC` function in `prog.cgi` stores user-supplied `SetDMZSettings/IPAddress` values in NVRAM via `nvram_safe_set("dmz_ipaddr", ...)`. These values are later retrieved in the `DMZ_run` function of `librcm.so` using `nvram_safe_get` and concatenated into `iptables` shell commands executed via `twsystem()` without any sanitization. An unauthenticated remote attacker can exploit this vulnerability to execute arbitrary commands on the device through specially crafted HTTP requests to the router's web interface.

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

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

It affects 1 product.


Products: Dlink Dir-882 Firmware.

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

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

## Is CVE-2025-60700 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-44804](https://insights.sbomify.com/CVE-2022-44804/): Memory corruption in n/a (critical 9.8)
- [CVE-2022-44806](https://insights.sbomify.com/CVE-2022-44806/): Memory corruption in n/a (critical 9.8)
- [CVE-2022-44807](https://insights.sbomify.com/CVE-2022-44807/): Memory corruption in n/a (critical 9.8)
- [CVE-2022-28895](https://insights.sbomify.com/CVE-2022-28895/): Command injection in n/a (critical 9.8)
- [CVE-2022-28896](https://insights.sbomify.com/CVE-2022-28896/): Command injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-60700 is a medium-severity command injection vulnerability in n/a, published on 13 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-60700 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-2025-60700/ (Markdown: https://insights.sbomify.com/CVE-2025-60700/index.md)
```

## Sources

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

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