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

> Authenticated attackers can execute arbitrary OS commands on Nexxt Solutions Mesh Routers via unsanitized firmware update parameters.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N`)
- **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:** 15 Jul 2025
- **Updated:** 15 Jul 2025
- **Also known as:** GHSA-v28v-mcvx-jj9g

## What is CVE-2025-52379?

CVE-2025-52379 is a medium-severity command injection vulnerability in n/a, published on 15 Jul 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Nexxt Solutions NCM-X1800 Mesh Router firmware UV1.2.7 and below contains an authenticated command injection vulnerability in the firmware update feature. The /web/um_fileName_set.cgi and /web/um_web_upgrade.cgi endpoints fail to properly sanitize the upgradeFileName parameter, allowing authenticated attackers to execute arbitrary OS commands on the device, resulting in remote code execution.

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

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


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

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

## Is CVE-2025-52379 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-52379 is a medium-severity command injection vulnerability in n/a, published on 15 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-52379 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-52379/ (Markdown: https://insights.sbomify.com/CVE-2025-52379/index.md)
```

## Sources

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

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