dbcve.org
Command InjectionWeakness · CWE-77

CVE-2026-6154

CRITICAL · 9.8 CVSS v3.1 Published 2026-04-13
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
A security flaw has been discovered in Totolink A7100RU 7.4cu.2313_b20191024. The affected element is the function setWizardCfg of the file /cgi-bin/cstecgi.cgi of the component CGI Handler. Performing a manipulation of the argument wizard results in os command injection. The attack may be initiated remotely. The exploit has been released to the public and may be used for attacks.

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

OS command injection vulnerability in Totolink A7100RU router firmware. The setWizardCfg function in /cgi-bin/cstecgi.cgi fails to sanitize the wizard parameter, allowing remote attackers to execute arbitrary OS commands. Public exploit available, CVSS 9.8 indicates trivial exploitability with no authentication required.

MitigationApply vendor firmware patch when available; temporarily restrict network access to the device's CGI interface or place device behind a firewall to reduce attack surface.

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 the installed firmware version
    Access the router web interface (typically 192.168.1.1) and navigate to System Status or Firmware Upgrade page to view the current firmware version string.
    Affected if The firmware version matches v7.4cu.2313_b20191024 exactly
  2. Confirm the CSTECGI CGI interface is accessible
    Attempt to access http://[router-ip]/cgi-bin/cstecgi.cgi from a network-connected host. A successful HTTP 200 response indicates the interface is reachable.
    Affected if The CGI interface responds and is accessible from the network
  3. Check if remote WAN management is enabled
    Log into the router admin panel and navigate to Management or Remote Access settings. Look for options labeled Remote Management, Remote Access, or WAN Access that enable administration over the internet.
    Affected if Remote management over WAN is enabled, exposing the interface to untrusted networks
  4. Inspect the wizard parameter handling
    If you have shell access (via telnet/ssh or firmware extraction), examine the /cgi-bin/cstecgi.cgi binary or its configuration for the setWizardCfg function and verify it processes the 'wizard' parameter without sanitization.
    Affected if The setWizardCfg function accepts the wizard parameter and passes it unsanitized to system calls

The device is affected if it runs firmware version v7.4cu.2313_b20191024 and has the web interface network-accessible (especially via WAN remote management), allowing the wizard parameter in setWizardCfg to be exploited for command injection.

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

Apply vendor firmware patch when available; temporarily restrict network access to the device's CGI interface or place device behind a firewall to reduce attack surface.

Recommended fix Moderate confidence

Latest firmware version available from Totolink for A7100RU (newer than 7.4cu.2313_b20191024)

  1. 1. Identify the current firmware version of the Totolink A7100RU device by accessing the web administration interface or checking the device label.
  2. 2. Navigate to the official Totolink support website at www.totolink.net and locate the downloads or support section for the A7100RU model.
  3. 3. Check for any firmware updates newer than version 7.4cu.2313_b20191024 that address security vulnerabilities.
  4. 4. Download the latest stable firmware version provided by Totolink.
  5. 5. Access the router's web administration panel and locate the firmware upgrade or system maintenance section.
  6. 6. Upload and apply the new firmware version following the manufacturer's instructions.
  7. 7. After the upgrade completes, verify the new firmware version is installed and confirm the device is functioning properly.
  8. 8. If no firmware update is available from Totolink, consider replacing the device with a newer model that receives active security support.
Caveat Firmware upgrades may reset router configuration to defaults; backup settings before upgrading and reconfigure after

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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