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

> Attackers can execute arbitrary commands on Ruijie RG-EW1800GX PRO routers via a crafted POST request to a Lua script.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 11 Dec 2025
- **Updated:** 12 Dec 2025
- **Also known as:** GHSA-fjxp-pgfq-cfr8

## What is CVE-2025-56122?

CVE-2025-56122 is a high-severity command injection vulnerability in n/a, published on 11 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

OS Command Injection vulnerability in Ruijie RG-EW1800GX PRO B11P226_EW1800GX-PRO_10223117 allowing attackers to execute arbitrary commands via a crafted POST request to the module_get in file /usr/local/lua/dev_sta/networkConnect.lua.

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

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

It affects 3 products.


Products: Ruijie Rg-Ew1800gx Firmware, Ruijie Rg-Ew1800gx Pro Firmware, Ruijie Rg-Ew300n Firmware.

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

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

## Is CVE-2025-56122 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-56091](https://insights.sbomify.com/CVE-2025-56091/): Command injection in n/a (high 8.8)
- [CVE-2025-56102](https://insights.sbomify.com/CVE-2025-56102/): Command injection in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-56122 is a high-severity command injection vulnerability in n/a, published on 11 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-56122 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-56122/ (Markdown: https://insights.sbomify.com/CVE-2025-56122/index.md)
```

## Sources

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

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