dbcve.org
Smg Gateway Management SoftwareApplication · Synway

CVE-2025-71284

CRITICAL · 9.8 CVSS v3.1 Published 2026-04-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
Synway SMG Gateway Management Software contains an OS command injection vulnerability in the RADIUS configuration endpoint at /en/9-2radius.php where the radius_address POST parameter is split and interpolated directly into a sed command without sanitization. An unauthenticated remote attacker can inject arbitrary shell commands by submitting a POST request with crafted radius_address, radius_address2, shared_secret2, source_ip, timeout, or retry parameters along with save=1 and enable_radius=1 to achieve remote code execution. Exploitation evidence was first observed by the Shadowserver Foundation on 2025-07-11 (UTC).

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 confidence

Synway SMG Gateway Management Software contains an OS command injection vulnerability in the RADIUS configuration endpoint at /en/9-2radius.php. The radius_address POST parameter is split and interpolated directly into a sed command without any sanitization, allowing unauthenticated attackers to inject arbitrary shell commands. Successful exploitation requires POST requests with save=1 and enable_radius=1 along with crafted parameters (radius_address, radius_address2, shared_secret2, source_ip, timeout, or retry) to achieve remote code execution.

MitigationApply vendor patches immediately when available; meanwhile, restrict network access to the management interface to trusted IPs only and consider disabling the RADIUS feature if not required, as exploitation is trivial and achieves unauthenticated RCE.

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
Smg Gateway Management SoftwareApplication
Affected:all versions

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. Confirm Synway SMG Gateway is accessible
    Identify if the Synway SMG Gateway Management Software web interface is running by accessing the management URL (typically on ports 80/443 or a vendor-defined port). Look for the Synway login page or management interface.
    Affected if The Synway SMG Gateway Management Software web interface is reachable on the network.
  2. Check for the vulnerable RADIUS endpoint
    Verify the existence of the /en/9-2radius.php endpoint by attempting to access it directly via HTTP/HTTPS POST request.
    Affected if The endpoint /en/9-2radius.php responds to requests, indicating the vulnerable script is present.
  3. Inspect RADIUS configuration state
    Examine the RADIUS configuration to determine if enable_radius is set to 1. This may be done by reviewing saved configuration files, checking the web interface RADIUS settings page, or inspecting the underlying configuration storage.
    Affected if RADIUS feature is enabled (enable_radius=1) in the configuration.
  4. Identify exposed management interface
    Determine if the management interface is exposed to untrusted networks by reviewing network firewall rules, access control lists, or listening services on the host.
    Affected if The management interface (port 80/443 or custom) is accessible from untrusted networks or the internet.

Users are affected if they have Synway SMG Gateway Management Software with the RADIUS feature enabled (enable_radius=1) and the management interface is accessible, since all versions contain the command injection vulnerability in the /en/9-2radius.php endpoint.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor patches immediately when available; meanwhile, restrict network access to the management interface to trusted IPs only and consider disabling the RADIUS feature if not required, as exploitation is trivial and achieves unauthenticated RCE.

Fix this in Smg Gateway Management Software Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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