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

> Attackers can escape the restricted SSH shell to gain root access on Mitrastar routers by injecting a shell command into the file display utility.

- **Severity:** High 8.4 (`CVSS:3.1/AV:L/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Aug 2025
- **Updated:** 4 Aug 2026
- **Also known as:** GHSA-8rhx-8c6r-v9q6

## What is CVE-2025-50753?

CVE-2025-50753 is a high-severity command injection vulnerability in n/a, published on 26 Aug 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Mitrastar GPT-2741GNAC-N2 devices are provided with access through ssh into a restricted default shell.The command "deviceinfo show file" is supposed to be used from restricted shell to show files and directories. By providing " /bin/sh" (quotes included) to the argument of this command will drop a root shell.

Weakness: CWE-250 (Execution with Unnecessary Privileges)

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


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

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

## Is CVE-2025-50753 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-50753 is a high-severity command injection vulnerability in n/a, published on 26 Aug 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-50753 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-50753/ (Markdown: https://insights.sbomify.com/CVE-2025-50753/index.md)
```

## Sources

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

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