dbcve.org
Operation And Maintenance Security Management SystemApplication · Sangfor

CVE-2026-1412

CRITICAL · 9.8 CVSS v3.1 Published 2026-01-26
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 has been found in Sangfor Operation and Maintenance Security Management System up to 3.0.12. The impacted element is an unknown function of the file /fort/audit/get_clip_img of the component HTTP POST Request Handler. Such manipulation of the argument frame/dirno leads to command injection. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used.

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 · moderate confidence

Command injection vulnerability in Sangfor Operation and Maintenance Security Management System's /fort/audit/get_clip_img endpoint. The frame/dirno parameters in HTTP POST requests are not properly sanitized, allowing remote attackers to inject and execute arbitrary operating system commands.

MitigationApply vendor patch or upgrade to version beyond 3.0.12 when available. Until then, restrict network access to the affected endpoint via firewall or web application firewall rules.

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 Operation and Maintenance Security Management System installation
    Review your installed software inventory or check running services on your servers for the Sangfor product
    Affected if The product is installed on the system
  2. Determine installed version
    Access the system administration interface or check product documentation for version information, then compare against the affected range <= 3.0.12
    Affected if The installed version is 3.0.12 or lower
  3. Verify vulnerable endpoint exists
    Check if the web application exposes the /fort/audit/get_clip_img endpoint by reviewing exposed URL paths or attempting to access the endpoint
    Affected if The endpoint /fort/audit/get_clip_img is accessible in the web application
  4. Confirm parameter accessibility
    Send a POST request to /fort/audit/get_clip_img and verify the frame and dirno parameters are accepted
    Affected if The frame or dirno parameters are accepted and processed by the endpoint
  5. Assess network exposure
    Determine if the endpoint is accessible from untrusted networks by reviewing firewall rules, WAF configurations, or network ACLs protecting the application
    Affected if The endpoint is reachable from external or untrusted networks without proper access restrictions

You are affected if Sangfor Operation and Maintenance Security Management System version 3.0.12 or lower is installed AND the /fort/audit/get_clip_img endpoint with frame/dirno parameters is accessible on your 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 a release after 3.0.12
Interim mitigation

Apply vendor patch or upgrade to version beyond 3.0.12 when available. Until then, restrict network access to the affected endpoint via firewall or web application firewall rules.

Recommended fix Moderate confidence

Version 3.0.13 or later

  1. Identify all deployed instances of Sangfor Operation and Maintenance Security Management System version 3.0.12 or earlier
  2. Backup current system configuration and data before performing any upgrade
  3. Upgrade the Sangfor Operation and Maintenance Security Management System to version 3.0.13 or later (the first fixed release after 3.0.12)
  4. After upgrade, verify the /fort/audit/get_clip_img endpoint is no longer vulnerable to command injection through frame/dirno parameters
  5. Monitor vendor security advisories for any subsequent security updates
Caveat Review Sangfor release notes for 3.0.13 to check for any configuration or feature changes that may require adjustment

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
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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