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

> Remote attackers can execute arbitrary commands on Netgear DC112A devices via the deviceName parameter in usb_adv.cgi.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Mar 2025
- **Updated:** 21 Apr 2025
- **Also known as:** GHSA-f45w-55jr-pvp2

## What is CVE-2025-28219?

CVE-2025-28219 is a critical command injection vulnerability in n/a, published on 28 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Netgear DC112A V1.0.0.64 has an OS command injection vulnerability in the usb_adv.cgi, which allows remote attackers to execute arbitrary commands via parameter "deviceName" passed to the binary through a POST request.

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

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

It affects 1 product.


Products: Netgear Dc112a Firmware.

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

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

## Is CVE-2025-28219 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-45611](https://insights.sbomify.com/CVE-2021-45611/): Memory corruption in n/a (critical 9.6)
- [CVE-2023-38925](https://insights.sbomify.com/CVE-2023-38925/): Memory corruption in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-28219 is a critical command injection vulnerability in n/a, published on 28 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-28219 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-2025-28219/ (Markdown: https://insights.sbomify.com/CVE-2025-28219/index.md)
```

## Sources

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

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