dbcve.org
Operation And Maintenance Security Management SystemApplication · Sangfor

CVE-2025-12916

CRITICAL · 9.8 CVSS v3.1 Published 2025-11-09
Fix available
A fix is available. Upgrade to 3.0.11 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 Security Management System 3.0. Impacted is an unknown function of the file /fort/portal_login of the component Frontend. This manipulation of the argument loginUrl causes command injection. The attack may be initiated remotely. The exploit has been publicly disclosed and may be utilized. Upgrading to version 3.0.11 and 3.0.12 is recommended to address this issue. It is advisable to upgrade the affected component.

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

A command injection vulnerability exists in Sangfor Operation and Maintenance Security Management System 3.0 in the /fort/portal_login endpoint. The loginUrl parameter is not properly sanitized, allowing an attacker to inject and execute arbitrary OS commands remotely.

MitigationUpgrade to version 3.0.11 or 3.0.12 immediately to remediate this critical command injection vulnerability. Since this can be exploited remotely with CVSS 9.8, restrict network access to the affected system until the patch is applied.

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, < 3.0.11

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 Operation and Maintenance Security Management System
    Locate the installation directory or check running services for 'Sangfor' or 'fort' related processes. This is typically deployed as a web application on a server.
    Affected if The system has Sangfor Operation and Maintenance Security Management System installed
  2. Check the installed version
    Access the application's admin interface, check the About/Help page, or inspect version files in the installation directory for a version number.
    Affected if The installed version is 3.0.0 through 3.0.10 (any version >= 3.0 but < 3.0.11)
  3. Verify the /fort/portal_login endpoint is accessible
    Attempt to access the URL path /fort/portal_login on the server (e.g., https://target/fort/portal_login). A 200 response or login form indicates the endpoint exists.
    Affected if The /fort/portal_login endpoint is exposed and responds to requests

The system is affected if Sangfor Operation and Maintenance Security Management System version 3.0 through 3.0.10 is installed and the /fort/portal_login endpoint is accessible on the network.

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.

dbcve · scoped
Upgrade available Upgrade to 3.0.11 or later
Fixed in 3.0.11
Interim mitigation

Upgrade to version 3.0.11 or 3.0.12 immediately to remediate this critical command injection vulnerability. Since this can be exploited remotely with CVSS 9.8, restrict network access to the affected system until the patch is applied.

Recommended fix High confidence

3.0.12

  1. Obtain the fixed version (3.0.11 or 3.0.12) from the official Sangfor vendor channels
  2. Perform a complete backup of the current system configuration and data
  3. Follow Sangfor's standard upgrade procedure for the Operation and Maintenance Security Management System
  4. Verify the upgrade was successful by checking the version number
  5. Test that the /fort/portal_login functionality works correctly post-upgrade
Caveat No specific breaking changes mentioned in the available documentation; upgrade within same minor version typically maintains compatibility

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Operation And Maintenance Security Management System Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,960
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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