dbcve.org
Command InjectionWeakness · CWE-77

CVE-2026-5678

HIGH · 7.3 CVSS v3.1 Published 2026-04-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
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 weakness has been identified in Totolink A7100RU 7.4cu.2313_b20191024. The affected element is the function setScheduleCfg of the file /cgi-bin/cstecgi.cgi. Executing a manipulation of the argument mode can lead to os command injection. The attack may be launched remotely. The exploit has been made available to the public and could 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 · moderate confidence

OS command injection vulnerability in Totolink A7100RU router firmware 7.4cu.2313_b20191024. The setScheduleCfg function in /cgi-bin/cstecgi.cgi fails to properly sanitize the 'mode' argument, allowing remote attackers to inject arbitrary OS commands via the CGI interface.

MitigationUpdate router firmware to a patched version if available; otherwise, restrict network access to the web management interface (port 80/443) or disable the device until a patch is released.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify device model
    Access the router's web interface or check the device label/metadata to confirm the model is Totolink A7100RU
    Affected if Device is not a Totolink A7100RU model
  2. Check CGI interface accessibility
    Verify that the web interface and /cgi-bin/cstecgi.cgi endpoint is reachable from the network
    Affected if The CGI interface is exposed and accessible
  3. Verify setScheduleCfg function exists
    Inspect the firmware or attempt a benign request to the cstecgi.cgi endpoint with the setScheduleCfg action to confirm the function is present
    Affected if The setScheduleCfg function is implemented in the firmware
  4. Confirm mode parameter is accepted
    Test whether the CGI endpoint accepts the 'mode' parameter in the setScheduleCfg action
    Affected if The 'mode' parameter is accepted by the CGI interface
  5. Compare firmware version
    Check the installed firmware version in the router's system settings or by extracting the firmware image; compare against any vendor-released version information
    Affected if Firmware version matches the affected range (if specified by vendor) or is an unpatched version

The environment is affected if the device is a Totolink A7100RU with accessible CGI interface where the setScheduleCfg function accepts a 'mode' parameter without proper sanitization.

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

Update router firmware to a patched version if available; otherwise, restrict network access to the web management interface (port 80/443) or disable the device until a patch is released.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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