dbcve.org
Command InjectionWeakness · CWE-77

CVE-2026-5692

HIGH · 7.3 CVSS v3.1 Published 2026-04-07
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 vulnerability was found in Totolink A7100RU 7.4cu.2313_b20191024. This impacts the function setGameSpeedCfg of the file /cgi-bin/cstecgi.cgi. The manipulation of the argument enable results in os command injection. The attack may be performed from remote. The exploit has been made public and could 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 setGameSpeedCfg function in /cgi-bin/cstecgi.cgi processes the 'enable' argument without input sanitization, allowing remote attackers to inject and execute arbitrary operating system commands via the manipulated parameter.

MitigationApply vendor firmware patch when available; until then, disable the affected CGI endpoint via firewall rules or network segmentation to prevent external access, as the vulnerability is remotely exploitable with a publicly available proof-of-concept.

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 router model
    Check the device label, web interface login page, or use network scanning tools (e.g., nmap) to fingerprint the device. Look for 'Totolink' or 'A7100RU' in HTTP Server headers, HTML title, or management page.
    Affected if The device is a Totolink A7100RU router.
  2. Confirm the vulnerable CGI endpoint is accessible
    Attempt to access http://<router-ip>/cgi-bin/cstecgi.cgi via curl or browser. Check if the endpoint responds (even with an error).
    Affected if The endpoint is reachable and returns a response, indicating the web interface is active.
  3. Determine if authentication is required for the CGI
    Send a request to /cgi-bin/cstecgi.cgi and inspect the HTTP response. Look for 401/403 status codes or authentication challenges. Try a request without credentials to see if the function accepts unauthenticated input.
    Affected if The setGameSpeedCfg function can be invoked without authentication or with default credentials.
  4. Inspect if setGameSpeedCfg function is exposed
    Send a POST request to /cgi-bin/cstecgi.cgi with a JSON body such as {'topicurl':'setGameSpeedCfg','enable':'test'} and observe the response. Check if the function is recognized or returns an error indicating the feature exists.
    Affected if The function is recognized and processes the 'enable' parameter.
  5. Test for command injection in the enable parameter
    Send a benign test payload in the 'enable' parameter (e.g., using command separators like ';' or '|'). Compare the response or behavior to determine if input is passed to the system shell unsanitized. Only do this in authorized, non-production environments.
    Affected if The router executes injected commands or exhibits unexpected behavior based on the payload, confirming the vulnerability.

If the device is a Totolink A7100RU with an accessible /cgi-bin/cstecgi.cgi endpoint where the setGameSpeedCfg function processes the 'enable' parameter without sanitization, the environment is affected by CVE-2026-5692.

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 when available; until then, disable the affected CGI endpoint via firewall rules or network segmentation to prevent external access, as the vulnerability is remotely exploitable with a publicly available proof-of-concept.

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-5692 — 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-5692 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