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

> Authenticated users can execute arbitrary shell commands as root on Ruijie APs via the web_action.do endpoint, leading to file disclosure and device disruption.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Dec 2025
- **Updated:** 5 Jul 2026
- **Also known as:** GHSA-6p5m-fhhh-365v

## What is CVE-2025-65363?

CVE-2025-65363 is a high-severity command injection vulnerability in n/a, published on 8 Dec 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Authenticated append-style command-injection Ruijie APs (AP_RGOS 11.1.x) allows an authenticated web user to execute appended shell expressions as root, enabling file disclosure, device disruption, and potential network pivoting via the command parameter to the web_action.do endpoint.

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

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

It affects 1 product.


Products: Ruijie Rg-Ap720-L Firmware.

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

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

## Is CVE-2025-65363 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-65363 is a high-severity command injection vulnerability in n/a, published on 8 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-65363 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-65363/ (Markdown: https://insights.sbomify.com/CVE-2025-65363/index.md)
```

## Sources

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

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