# CVE-2025-15501: Sangfor Operation and Maintenance Management System getCmd WriterHandle.getCmd os command injection

> Remote attackers can execute arbitrary OS commands via the getCmd function in Sangfor Operation and Maintenance Management System.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Jan 2026
- **Updated:** 23 Feb 2026
- **Also known as:** GHSA-hj59-mf6x-2j8w

## What is CVE-2025-15501?

CVE-2025-15501 is a critical command injection vulnerability in Sangfor Operation and Maintenance Management System, published on 9 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was determined in Sangfor Operation and Maintenance Management System up to 3.0.8. Impacted is the function WriterHandle.getCmd of the file /isomp-protocol/protocol/getCmd. This manipulation of the argument sessionPath causes os command injection. Remote exploitation of the attack is possible. The exploit has been publicly disclosed and may be utilized. The vendor was contacted early about this disclosure but did not respond in any way.

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

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

It affects 1 product.


Products: Sangfor Operation and Maintenance Security Management System.

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

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

## Is CVE-2025-15501 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-15501 exists.

## Other vulnerabilities in Sangfor Operation and Maintenance Management System

- [CVE-2026-1324](https://insights.sbomify.com/CVE-2026-1324/): Sangfor Operation and Maintenance Management System SSH Protocol session SessionController os command injection (high 8.7)
- [CVE-2026-1412](https://insights.sbomify.com/CVE-2026-1412/): Sangfor Operation and Maintenance Security Management System HTTP POST Request get_clip_img command injection (medium 6.9)
- [CVE-2026-1325](https://insights.sbomify.com/CVE-2026-1325/): Sangfor Operation and Maintenance Security Management System edit_pwd_mall password recovery (medium 6.9)
- [CVE-2025-15502](https://insights.sbomify.com/CVE-2025-15502/): Sangfor Operation and Maintenance Management System session SessionController os command injection (medium 6.9)
- [CVE-2025-15503](https://insights.sbomify.com/CVE-2025-15503/): Sangfor Operation and Maintenance Management System common.jsp unrestricted upload (medium 6.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-15501 is a critical command injection vulnerability in Sangfor Operation and Maintenance Management System, published on 9 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-15501 exists.

Affected product: Sangfor Operation and Maintenance Management System. 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-15501/ (Markdown: https://insights.sbomify.com/CVE-2025-15501/index.md)
```

## Sources

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

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