CVE-2025-1536
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 found in Raisecom Multi-Service Intelligent Gateway up to 20250208. It has been declared as critical. This vulnerability affects unknown code of the file /vpn/vpn_template_style.php of the component Request Parameter Handler. The manipulation of the argument stylenum leads to os command injection. The attack can 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.
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 Raisecom Multi-Service Intelligent Gateway (up to 20250208) in the /vpn/vpn_template_style.php file. The 'stylenum' request parameter is not properly sanitized before being passed to system shell execution, allowing remote attackers to inject arbitrary OS commands. Public exploit available and 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.
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
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
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.
-
Identify Raisecom Multi-Service Intelligent GatewayAccess the device management interface or check the system information page to confirm the device model is Raisecom Multi-Service Intelligent GatewayAffected if The device is a Raisecom Multi-Service Intelligent Gateway
-
Check firmware versionLocate the firmware version in the device's web interface under System > Firmware/Version, or check via CLI with 'show version' or similar commandAffected if The firmware version is 20250208 or earlier
-
Verify vulnerable endpoint existsAttempt to access the URL path /vpn/vpn_template_style.php on the device's web server (e.g., http://<device-ip>/vpn/vpn_template_style.php)Affected if The endpoint returns a valid HTTP response (200 or other) rather than a 404 error
-
Confirm VPN templating feature is enabledCheck the device configuration for VPN settings, specifically look for VPN template or VPN template style configuration options in the web interface under VPN settingsAffected if VPN templating feature is accessible and not explicitly disabled in the configuration
-
Test parameter accessibilitySend a request to /vpn/vpn_template_style.php with a test 'stylenum' parameter (e.g., stylenum=test) and observe if the parameter is processed without causing a validation errorAffected if The 'stylenum' parameter is accepted and processed by the application
If the device is a Raisecom Multi-Service Intelligent Gateway with firmware version 20250208 or earlier and the /vpn/vpn_template_style.php endpoint is accessible, the device is likely affected by this command injection vulnerability.
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 dataSince no vendor patch is available, implement network segmentation to isolate the affected device from untrusted networks and apply strict firewall rules to limit access to the management interface. Consider disabling the VPN templating feature if not required.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.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 $7,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-1536 — 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-1536 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