CVE-2025-15502
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 · uneditedA vulnerability was identified in Sangfor Operation and Maintenance Management System up to 3.0.8. The affected element is the function SessionController of the file /isomp-protocol/protocol/session. Such manipulation of the argument Hostname leads to os command injection. The attack can be executed 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 confidenceOS command injection vulnerability in Sangfor Operation and Maintenance Management System's SessionController function within /isomp-protocol/protocol/session. The Hostname parameter is not properly sanitized, allowing remote attackers to inject arbitrary OS commands without authentication. The exploit is publicly available and the vendor did not respond to disclosure.
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<= 3.0.8CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Sangfor product is deployedLocate the Sangfor Operation and Maintenance Security Management System installation by checking for the /isomp-protocol directory or the product's web interface accessible on the management port (typically 443 or 8443).Affected if The system is running Sangfor Operation and Maintenance Security Management System.
-
Identify installed versionAccess the system's about page, administrative console, or check version files in the installation directory. Compare the version number to the affected range.Affected if The installed version is 3.0.8 or any earlier version.
-
Verify vulnerable endpoint is exposedConfirm the /isomp-protocol/protocol/session endpoint is reachable by attempting an HTTP request to this path. This is the SessionController function location.Affected if The endpoint responds and accepts parameters.
-
Check for command injection indicatorsReview web server logs and application logs for unusual patterns in the Hostname parameter, such as presence of shell metacharacters (| ; $ ` or command sequences). Also check for unexpected outbound connections or new processes.Affected if Log entries show shell metacharacters in Hostname parameter submissions, or unexpected system behavior following such requests.
The environment is affected if Sangfor Operation and Maintenance Security Management System version 3.0.8 or lower is installed and the /isomp-protocol/protocol/session endpoint is accessible, with potential compromise indicated by command injection patterns in logs.
Generated from the published advisory. Verify against your own configuration.
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 dataApply input validation/sanitization to the Hostname parameter in the SessionController function to prevent command injection. Until a vendor patch is available, restrict network access to the affected system and monitor for exploitation attempts.
- Consultation3.0 h
- Implementation4.0 h
- Testing5.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-15502 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-15502 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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