Security readout for executives and security teams
Plain-English summary
CVE-2026-1414 affects Sangfor Operation and Maintenance Security Management System versions 3.0.0 through 3.0.12. A remote authenticated attacker may inject operating-system commands through a management endpoint. Public disclosure of an exploit is reported, but the provided sources do not show confirmed active exploitation.
Executive priority
Treat as a near-term remediation item for any reachable Sangfor OSM deployment. Business urgency rises if the system manages sensitive infrastructure, is internet-facing, or has many internal users with access.
Technical view
The flaw is a command injection issue in the getInformation function of /equipment/get_Information, triggered through the fortEquipmentIp argument in an HTTP POST request handler. VulDB maps it to CWE-74 and CWE-77. CVSS v2 is 6.5 with network access, low complexity, and single authentication required.
Likely exposure
Exposure is limited to organizations running Sangfor Operation and Maintenance Security Management System 3.0.0 through 3.0.12, especially where the management interface is reachable by untrusted users or broad internal networks.
Exploitation context
The source bundle says the attack can be launched remotely and that exploit details were publicly disclosed. CVSS indicates authentication is required. There is no KEV listing and no cited evidence of active exploitation in the provided sources.
Researcher notes
Evidence is primarily from CVE and VulDB records. The bundle reports public exploit disclosure, but one GitHub reference is marked broken and no vendor remediation details are included. Do not assume a fixed version without Sangfor confirmation.
Mitigation direction
- Check Sangfor vendor guidance for fixed versions or official workarounds.
- Restrict access to the Sangfor management interface to trusted administration networks.
- Require strong authentication and review administrative account exposure.
- Monitor HTTP POST activity to the affected management endpoint.
- Prioritize upgrade or compensating controls for internet-reachable deployments.
Validation and detection
- Inventory Sangfor OSM deployments and record exact versions.
- Identify systems running versions 3.0.0 through 3.0.12.
- Confirm whether the management interface is exposed beyond trusted administrators.
- Review logs for unusual requests to /equipment/get_Information.
- Check whether vendor patches or advisories have become available.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-74: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-77: Command execution behavior lookup
Command injection weaknesses can lead defenders to review execution techniques and command interpreter telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-1414 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.5 (2.0)
- Known Exploited
- No
- Published
Vector: AV:N/AC:L/Au:S/C:P/I:P/A:P/E:POC/RL:ND/RC:UR
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
AV:N/AC:L/Au:S/C:P/I:P/A:P/E:POC/RL:ND/RC:UR86.4Primary CVE scoreVulnerability scoring details
Base CVSS 2.0 score
6.5MediumVector: AV:N/AC:L/Au:S/C:P/I:P/A:P/E:POC/RL:ND/RC:UR
Source materials
- CVE List V5 sourceCVE List V5
- VDB-342803 | Sangfor Operation and Maintenance Security Management System HTTP POST Request get_Information getInformation command injectionCVE reference · vdb-entry, technical-description
- VDB-342803 | CTI Indicators (IOB, IOC, TTP, IOA)CVE reference · signature, permissions-required
- Submit #736524 | Sangfor Operation and Maintenance Security Management System (OSM / 运维安全管理系统) v3.0.12 Command InjectionCVE reference · third-party-advisory
- https://github.com/LX-LX88/cve/issues/24CVE reference · broken-link, exploit
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')
Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Neutralization of Special Elements used in a Command ('Command Injection')
Improper Neutralization of Special Elements used in a Command ('Command Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.