dbcve.org
Command InjectionWeakness · CWE-77

CVE-2026-5690

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 flaw has been found in Totolink A7100RU 7.4cu.2313_b20191024. The impacted element is the function setRemoteCfg of the file /cgi-bin/cstecgi.cgi. Executing a manipulation of the argument enable can lead to os command injection. The attack can be executed remotely. The exploit has been published and may be used.

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 7.4cu.2313_b20191024. The setRemoteCfg function in /cgi-bin/cstecgi.cgi fails to sanitize the 'enable' parameter, allowing remote attackers to execute arbitrary OS commands via the web interface.

MitigationApply vendor firmware patch if available; if no patch exists, disable remote management access from untrusted networks or replace the device.

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 the device model
    Access the router admin web interface or check the device label to confirm it is a Totolink A7100RU model.
    Affected if The device is not a Totolink A7100RU router.
  2. Check the firmware version
    Log into the router web interface and navigate to the Status or System Information page to view the installed firmware version. Alternatively, check the firmware file name if you have access to the firmware binary.
    Affected if The firmware version is 7.4cu.2313_b20191024 (the affected version).
  3. Verify the vulnerable CGI binary exists
    Attempt to access the file /cgi-bin/cstecgi.cgi via the router web interface or check the firmware filesystem if you can extract it.
    Affected if The file /cgi-bin/cstecgi.cgi does not exist on the device.
  4. Confirm remote management is enabled
    In the router web interface, look for 'Remote Management', 'Remote Access', or 'TR-069' settings under the Administration or Advanced settings. Check if the 'enable' option for remote management is turned on.
    Affected if Remote management is enabled and accessible.
  5. Check network exposure of the web interface
    Determine if the router admin interface (port 80/443) is reachable from the internet by attempting an external connection test or reviewing firewall rules.
    Affected if The router web interface is exposed directly to the internet.

You are affected if you have a Totolink A7100RU router running firmware version 7.4cu.2313_b20191024 with the vulnerable /cgi-bin/cstecgi.cgi binary present and remote management enabled or the web interface exposed externally.

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 firmware patch if available; if no patch exists, disable remote management access from untrusted networks or replace the device.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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