# CVE-2023-26800: Command injection in n/a

> Attackers can execute arbitrary commands on Ruijie wireless routers via the upgradeConfirm function's path parameter.

- **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:** 26 Mar 2023
- **Updated:** 20 Feb 2025
- **Also known as:** GHSA-7p5g-53rx-5g9w

## What is CVE-2023-26800?

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

### Official description

Ruijie Networks RG-EW1200 Wireless Routers EW_3.0(1)B11P204 was discovered to contain a command injetion vulnerability via the params.path parameter in the upgradeConfirm function.

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

## Which versions are affected by CVE-2023-26800?

It affects 3 products.


Products: Ruijienetworks Rg-Ew1200 Firmware, Ruijienetworks Rg-Ew1200g Pro Firmware, Ruijienetworks Rg-Ew1200r Firmware.

## How do I fix CVE-2023-26800?

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

## Is CVE-2023-26800 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-26800 and fix it if it is affected.

What it is: CVE-2023-26800 is a critical command injection vulnerability in n/a, published on 26 Mar 2023. 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-2023-26800 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-2023-26800/ (Markdown: https://insights.sbomify.com/CVE-2023-26800/index.md)
```

## Sources

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

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