Skip to main content
Public proof of concept

CVE-2025-15499

Sangfor Operation and Maintenance Management System VersionController.java uploadCN os command injection

A public proof of concept exists; no exploitation attested.

  • Published2026-01-09
  • WeaknessCWE-77 · CWE-78

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

A vulnerability has been found in Sangfor Operation and Maintenance Management System up to 3.0.8. This vulnerability affects the function uploadCN of the file VersionController.java. The manipulation of the argument filename leads to os command injection. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Timeline

dates in UTC
  1. 2026-01-0922:15CVE publishedNVD

Versions per branch

NVD
Sangfor operation and maintenance management system
BranchAffectedFixed in
3.0≤ 3.0.8no fix published

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA1 product

As VulDB, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • Sangfor Operation and Maintenance Management System
    Affected
    • = 3.0.0no fix stated
    • = 3.0.1no fix stated
    • = 3.0.2no fix stated
    • = 3.0.3no fix stated
    • = 3.0.4no fix stated
    • = 3.0.5no fix stated
    • = 3.0.6no fix stated
    • = 3.0.7no fix stated

    1 more version line in the CVE record.

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2026-02-23

Fix

No fix published by the sources we read yet. NVD record

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

  • CISA-ADPSSVC decisionpoc2026-01-09
  • CNACVSS 4.07.4known since 2026-10-23
  • CNACVSS 3.18.8known since 2026-10-23
  • NVDCVSS 3.19.8read 2026-10-23
  • CNACVSS 2.09known since 2026-10-23
  • CNAweakness (CWE)CWE-77, CWE-78known since 2026-10-23
  • NVDweakness (CWE)CWE-78read 2026-10-23
  • FIRST EPSSEPSS score5.7 %2026-11-08
  • GitHub Advisoriesadvisory—

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CVSS 4.0 vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Published
2026-01-09
Last Modified
2026-06-17
NVD status
Analyzed
GitHub Advisory
GHSA-8mvr-hqm9-fqrf

Frequently asked questions

What is CVE-2025-15499?

A vulnerability has been found in Sangfor Operation and Maintenance Management System up to 3.0.8. This vulnerability affects the function uploadCN of the file VersionController.java. The manipulation of the argument filename leads to os command injection. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Is CVE-2025-15499 actively exploited?

A proof-of-concept exploit exists for CVE-2025-15499, but active exploitation has not been confirmed at this time.

What is the CVSS score for CVE-2025-15499?

CVE-2025-15499 has a CVSS v3 base score of 9.8 (CRITICAL severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.

Running Sangfor Operation and? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, November 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database

Sources for this record