dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2025-8890

CRITICAL · 9.3 CVSS v4.0 Published 2025-11-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
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
Firmware in SDMC NE6037 routers prior to version 7.1.12.2.44 has a network diagnostics tool vulnerable to a shell command injection attacks. In order to exploit this vulnerability, an attacker has to log in to the router's administrative portal, which by default is reachable only via LAN ports.

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 · moderate confidence

The SDMC NE6037 router firmware contains a shell command injection vulnerability in its network diagnostics tool. An authenticated attacker with administrative portal access can inject arbitrary shell commands through the diagnostics feature, potentially achieving full device compromise with root privileges.

MitigationUpgrade router firmware to version 7.1.12.2.44 or later to patch the vulnerability. Until patched, limit administrative portal access to trusted users only and disable the network diagnostics tool if possible.

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
Adjacent
Complexity
Low
Privileges
High
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:A/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/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

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 the router model
    Access the router's web administrative interface or check the device label/marketing materials to confirm the model is SDMC NE6037
    Affected if The device is an SDMC NE6037 router
  2. Check the installed firmware version
    Log into the router's administrative interface and navigate to the system status or firmware information page to view the current firmware version. Compare it to the fixed version 7.1.12.2.44
    Affected if The firmware version is lower than 7.1.12.2.44
  3. Verify if network diagnostics feature is accessible
    Locate the network diagnostics or ping/traceroute tool within the router's administrative interface. Determine if this feature is present and available to authenticated users
    Affected if The network diagnostics feature is present and accessible to authenticated users
  4. Confirm administrative interface accessibility
    Check if the router's web administrative portal is reachable from LAN ports. Verify whether any IP-based access restrictions or remote management settings are configured
    Affected if The administrative interface is accessible from LAN ports without strict IP restrictions

A user is affected if they have an SDMC NE6037 router running firmware version lower than 7.1.12.2.44 with the network diagnostics feature accessible through the administrative interface.

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

Upgrade router firmware to version 7.1.12.2.44 or later to patch the vulnerability. Until patched, limit administrative portal access to trusted users only and disable the network diagnostics tool if possible.

Recommended fix High confidence

7.1.12.2.44

  1. 1. Obtain the firmware version 7.1.12.2.44 or later from the official SDMC support channel or the vendor's website
  2. 2. Access the router's administrative web interface by navigating to the router's LAN IP address (e.g., 192.168.1.1)
  3. 3. Log in with administrative credentials
  4. 4. Navigate to the firmware upgrade or system settings section of the admin interface
  5. 5. Upload the downloaded firmware file (7.1.12.2.44 or later) and initiate the upgrade
  6. 6. Wait for the upgrade process to complete and the router to reboot
  7. 7. Verify the firmware version has been updated in the router's admin interface

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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