dbcve.org
Operation And Maintenance Security Management SystemApplication · Sangfor

CVE-2025-15501

CRITICAL · 9.8 CVSS v3.1 Published 2026-01-09
Fix available
A fix is available. Upgrade to after 3.0.8 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

OS command injection vulnerability in Sangfor Operation and Maintenance Management System (versions up to 3.0.8). The WriterHandle.getCmd function in /isomp-protocol/protocol/getCmd accepts user-controlled input through the sessionPath parameter without proper sanitization, allowing remote attackers to execute arbitrary operating system commands.

MitigationSince the vendor did not respond to early disclosure and no patch is available, implement compensating controls immediately: restrict network access to the affected system, deploy WAF rules to detect and block command injection payloads in the sessionPath parameter, and consider isolating the system until a vendor patch becomes available.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Operation And Maintenance Security Management SystemApplication
Affected:<= 3.0.8

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm the product is Sangfor Operation and Maintenance Management System
    Access the web interface or check system documentation to verify the product name matches 'Sangfor Operation and Maintenance Security Management System' or 'Sangfor O&M System'
    Affected if The installed product is Sangfor Operation and Maintenance Management System
  2. Identify the installed version
    Check the system about page, version info in the admin panel, or look for version files in the installation directory. The version is typically displayed in the UI footer or in a /about endpoint
    Affected if The version number is 3.0.8 or lower (any version up to and including 3.0.8)
  3. Verify the vulnerable endpoint exists
    Attempt to access the URL path /isomp-protocol/protocol/getCmd on the server (requires authentication). Check if the endpoint responds or returns an error related to 'WriterHandle' or 'getCmd'
    Affected if The endpoint /isomp-protocol/protocol/getCmd is accessible and responds to requests
  4. Check if the protocol module is enabled
    Examine the system configuration files or admin panel settings to verify if the protocol handling module (isomp-protocol) is enabled and accessible
    Affected if The protocol module handling /isomp-protocol requests is enabled in the system configuration

If the system is Sangfor O&M Management System version 3.0.8 or lower AND the /isomp-protocol/protocol/getCmd endpoint is accessible, the environment is affected by CVE-2025-15501.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 3.0.8
Interim mitigation

Since the vendor did not respond to early disclosure and no patch is available, implement compensating controls immediately: restrict network access to the affected system, deploy WAF rules to detect and block command injection payloads in the sessionPath parameter, and consider isolating the system until a vendor patch becomes available.

Fix this in Operation And Maintenance Security Management System Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,360
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,776.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-15501 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-15501 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data