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

> Attackers can execute arbitrary commands on Ruijie RG-YST Access Points via a crafted POST request to the password modification endpoint.

- **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-8x78-jw4j-7jp6

## What is CVE-2025-56099?

CVE-2025-56099 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-YST AP_3.0(1)B11P280YST250F allowing attackers to execute arbitrary commands via a crafted POST request to the pwdmodify in file /usr/lib/lua/luci/modules/common.lua.

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

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

It affects 4 products.


Products: Ruijie Reyee Os, Ruijie Rg-Eap602 Firmware, Ruijie Rg-Est310 V2 Firmware, Ruijie Rg-Yst250f Firmware.

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

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

## Is CVE-2025-56099 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-42936](https://insights.sbomify.com/CVE-2024-42936/): Code injection in n/a (critical 9.8)
- [CVE-2025-56083](https://insights.sbomify.com/CVE-2025-56083/): Command injection in n/a (high 8.8)
- [CVE-2025-56084](https://insights.sbomify.com/CVE-2025-56084/): Command injection in n/a (high 8.8)
- [CVE-2025-56113](https://insights.sbomify.com/CVE-2025-56113/): Command injection in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-56099 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-56099 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-56099/ (Markdown: https://insights.sbomify.com/CVE-2025-56099/index.md)
```

## Sources

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

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