# CVE-2025-59370: Command injection in Router

> A remote authenticated attacker can execute arbitrary commands on ASUS routers via a command injection flaw in bwdpi.

- **Severity:** High 7.5 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Nov 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-4fgj-hr8q-rhjw

## What is CVE-2025-59370?

CVE-2025-59370 is a high-severity command injection vulnerability in ASUS Router, published on 25 Nov 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A command injection vulnerability has been identified in bwdpi. A remote, authenticated attacker could leverage this vulnerability to potentially execute arbitrary commands, leading to the device executing unintended instructions.
Refer to the 'Security Update for ASUS Router Firmware' section on the ASUS Security Advisory for more information.

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

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


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

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

## Is CVE-2025-59370 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-59370 is a high-severity command injection vulnerability in ASUS Router, published on 25 Nov 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-59370 in the wild and no public exploit code.

Affected product: ASUS Router. 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-59370/ (Markdown: https://insights.sbomify.com/CVE-2025-59370/index.md)
```

## Sources

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

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