dbcve.org
Command InjectionWeakness · CWE-77

CVE-2026-6115

CRITICAL · 9.8 CVSS v3.1 Published 2026-04-12
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 flaw has been found in Totolink A7100RU 7.4cu.2313_b20191024. This affects the function setAppCfg of the file /cgi-bin/cstecgi.cgi of the component CGI Handler. Executing a manipulation of the argument enable can lead to os command injection. The attack may be launched 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 setAppCfg function in the CGI handler (/cgi-bin/cstecgi.cgi) fails to sanitize the 'enable' argument, allowing remote attackers to execute arbitrary OS commands.

MitigationApply vendor firmware patch if available; otherwise restrict network access to the CGI interface via firewall rules or disable the affected service to reduce exposure.

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 router model
    Check the device label or admin interface for the model name (Totolink A7100RU)
    Affected if Device is not a Totolink A7100RU router (not affected)
  2. Check firmware version
    Access the router admin panel (typically at 192.168.0.1) and look under System Status or Firmware Upgrade to find the installed firmware version; compare to 7.4cu.2313_b20191024
    Affected if Firmware version matches or predates 7.4cu.2313_b20191024
  3. Verify CGI binary exists
    Attempt to access http://<router-ip>/cgi-bin/cstecgi.cgi via HTTP GET or POST - this endpoint should exist on vulnerable firmware
    Affected if The cstecgi.cgi endpoint responds (vulnerable binary is present)
  4. Confirm remote management is enabled
    In the router admin panel, check under Advanced or Security settings for 'Remote Management', 'Web Management', or 'TR-069' settings - determine if remote access from WAN is enabled
    Affected if Remote management/WAN access to the web interface is enabled (vulnerability is exploitable remotely)
  5. Check WAN exposure
    From an external network (not LAN), attempt to reach the router's public IP on port 80/443, or check router firewall rules to see if WAN HTTP/HTTPS ports are open
    Affected if The router admin interface is exposed to the internet or untrusted networks

The device is affected if it is a Totolink A7100RU running firmware 7.4cu.2313_b20191024 or earlier, with the cstecgi.cgi endpoint present and remote management exposed to untrusted networks.

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; otherwise restrict network access to the CGI interface via firewall rules or disable the affected service to reduce exposure.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,970
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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