dbcve.org
Operation And Maintenance Security Management SystemApplication · Sangfor

CVE-2026-1324

CRITICAL · 9.8 CVSS v3.1 Published 2026-01-22
Fix available
A fix is available. Upgrade to after 3.0.12 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 identified in Sangfor Operation and Maintenance Management System up to 3.0.12. Affected by this issue is the function SessionController of the file /isomp-protocol/protocol/session of the component SSH Protocol Handler. The manipulation of the argument keypassword leads to os command injection. It is possible to initiate the attack remotely. The exploit is publicly available and might be used. 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

Critical command injection vulnerability in Sangfor Operation and Maintenance Management System (up to v3.0.12) allows remote attackers to execute arbitrary OS commands via the SessionController component in the SSH Protocol Handler. The 'keypassword' argument is not properly sanitized before being used in system calls, enabling pre-authentication RCE. Public exploits are available.

MitigationApply vendor patch immediately when available; until then, restrict network access to the management interface, implement WAF rules to block command injection patterns in SSH parameters, and consider isolating the system from untrusted networks.

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.12

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. Identify Sangfor O&M Management System presence
    Scan your network for the Sangfor Operation and Maintenance Management System web interface - typically on ports 80, 443, 8080, or 8443. Check bannergrabbing or SSL certificates for 'Sangfor' or 'Sangfor O&M' identifiers.
    Affected if The system is found running on your network with the Sangfor O&M web interface accessible.
  2. Determine installed software version
    Log into the management console or check the '/about' or '/systeminfo' endpoints in the web UI. Alternatively, check HTTP response headers or the login page footer for the version number (e.g., v3.0.x).
    Affected if The displayed version is 3.0.12 or any earlier version (e.g., 3.0.11, 3.0.10, 2.x, etc.).
  3. Verify SSH Protocol Handler is exposed
    Attempt to connect to the system on port 22 (or configured SSH port) to confirm the SSH management interface is accessible from your network location. Check if the SessionController component handles SSH sessions.
    Affected if The SSH management interface is reachable and the SessionController component processes SSH protocol connections.
  4. Confirm vulnerability trigger point accessible
    Attempt a test request to the SessionController endpoint with the 'keypassword' parameter (e.g., viaBurp Suite or curl). The parameter should be accepted without authentication in the SSH Protocol Handler.
    Affected if The 'keypassword' parameter in the SSH Protocol Handler accepts unauthenticated input and the request reaches the SessionController component.

Your environment is affected if the Sangfor O&M Management System is present with version 3.0.12 or lower AND the SSH Protocol Handler with the SessionController component is network-accessible, allowing unauthenticated 'keypassword' parameter injection.

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.12
Interim mitigation

Apply vendor patch immediately when available; until then, restrict network access to the management interface, implement WAF rules to block command injection patterns in SSH parameters, and consider isolating the system from untrusted networks.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-1324 — 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-2026-1324 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