dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2025-6559

CRITICAL · 9.8 CVSS v3.1 Published 2025-06-24
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
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
Multiple wireless router models from Sapido have an OS Command Injection vulnerability, allowing unauthenticated remote attackers to inject arbitrary OS commands and execute them on the server. The affected models are out of support; replacing the device is recommended.

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

Multiple Sapido wireless router models contain an OS Command Injection vulnerability that allows unauthenticated remote attackers to inject and execute arbitrary operating system commands on the affected devices. This critical flaw (CVSS 9.8) affects out-of-support router firmware, enabling full compromise of the device without any authentication credentials.

MitigationSince the affected devices are end-of-life and receive no security updates, the vendor recommends replacing them with supported hardware. Until replacement, network segmentation and blocking of external access to router management interfaces may reduce exposure.

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
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. Identify Sapido router models in your network
    Review your network device inventory or physically inspect routers for Sapido branding. Check DHCP server logs, network scans, or access point configurations for Sapido device MAC addresses or hostnames.
    Affected if Any Sapido wireless router model is present in your environment.
  2. Determine router firmware version
    Access the router administration interface (typically via web browser at 192.168.1.1 or similar). Navigate to System Status, Firmware Upgrade, or About section to view the installed firmware version. This may also be displayed on the device label or available via SNMP queries.
    Affected if The installed firmware version matches or predates any known vulnerable Sapido firmware releases.
  3. Check if remote management is enabled
    Log into the router web interface and locate Remote Management, Remote Access, or WAN Access settings (usually under Advanced, Security, or Administration menus). Verify whether the HTTP/HTTPS management interface is accessible from the WAN/internet side.
    Affected if Remote management or WAN access to the router administration interface is enabled and exposed to untrusted networks.
  4. Verify network exposure of router admin interface
    Scan your external IP ranges for open HTTP/HTTPS ports (80, 443, 8080, 8443) responding to router login pages. Use external port scanning tools or review firewall rules to determine if the router management interface is reachable from the internet.
    Affected if The router administration interface is directly accessible from the internet without VPN or network segmentation.

Your environment is affected if you have any Sapido wireless routers with firmware that matches the vulnerable versions and their management interfaces are remotely accessible.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Since the affected devices are end-of-life and receive no security updates, the vendor recommends replacing them with supported hardware. Until replacement, network segmentation and blocking of external access to router management interfaces may reduce exposure.

Recommended fix High confidence
  1. 1. Identify all Sapido wireless router models in use that may be affected by CVE-2025-6559.
  2. 2. Since the affected models are out of support and no firmware patches are available, the vendor recommends replacing the affected devices with newer, supported models.
  3. 3. If immediate replacement is not possible, consider network segmentation to isolate affected devices and restrict external access to them.
  4. 4. Implement additional monitoring for any suspicious activity targeting these devices.
  5. 5. Plan for replacement of affected devices with vendor-supported alternatives.
Caveat Device replacement required; no firmware update available as models are end-of-life

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing3.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,050
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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