# CVE-2025-15503: Sangfor Operation and Maintenance Management System common.jsp unrestricted upload

> Remote attackers can upload arbitrary files via the common.jsp endpoint in Sangfor O&M System, potentially leading to code execution.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/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:** 10 Jan 2026
- **Updated:** 23 Feb 2026
- **Also known as:** GHSA-h49h-jpp7-xv85

## What is CVE-2025-15503?

CVE-2025-15503 is a medium-severity vulnerability in Sangfor Operation and Maintenance Management System, published on 10 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A security flaw has been discovered in Sangfor Operation and Maintenance Management System up to 3.0.8. The impacted element is an unknown function of the file /fort/trust/version/common/common.jsp. Performing a manipulation of the argument File results in unrestricted upload. The attack is possible to be carried out remotely. The exploit has been released to the public and may be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type), CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Sangfor Operation and Maintenance Security Management System.

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

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

## Is CVE-2025-15503 being exploited?

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

Public exploit code:

- Sangfor OSM - Arbitrary File Upload (nuclei): http/cves/2025/CVE-2025-15503.yaml

## Other vulnerabilities in Sangfor Operation and Maintenance Management System

- [CVE-2025-15501](https://insights.sbomify.com/CVE-2025-15501/): Sangfor Operation and Maintenance Management System getCmd WriterHandle.getCmd os command injection (critical 9.3)
- [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)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-15503 is a medium-severity vulnerability in Sangfor Operation and Maintenance Management System, published on 10 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-15503 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-15503/ (Markdown: https://insights.sbomify.com/CVE-2025-15503/index.md)
```

## Sources

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

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