# CVE-2025-68459: Command injection in AP180(JA) V1.xx

> An authenticated attacker can execute arbitrary OS commands on Ruijie AP180 series devices via the CLI service.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Dec 2025
- **Updated:** 18 Dec 2025
- **Also known as:** GHSA-fww6-h55r-7gx6

## What is CVE-2025-68459?

CVE-2025-68459 is a high-severity command injection vulnerability in Ruijie Networks Co., Ltd. AP180(JA) V1.xx, published on 18 Dec 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

RG - AP180, Indoor Wall Plate Wireless AP AP180 series provided by Ruijie Networks Co., Ltd. contain an OS command injection vulnerability. An arbitrary OS command may be executed on the product by an attacker who logs in to the CLI service.

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

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


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

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

## Is CVE-2025-68459 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-68459 is a high-severity command injection vulnerability in Ruijie Networks Co., Ltd. AP180(JA) V1.xx, published on 18 Dec 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-68459 in the wild and no public exploit code.

Affected product: Ruijie Networks Co., Ltd. AP180(JA) V1.xx. 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-68459/ (Markdown: https://insights.sbomify.com/CVE-2025-68459/index.md)
```

## Sources

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

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