CVE-2026-6114
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 · uneditedA vulnerability was detected in Totolink A7100RU 7.4cu.2313_b20191024. Affected by this issue is the function setNetworkCfg of the file /cgi-bin/cstecgi.cgi of the component CGI Handler. Performing a manipulation of the argument proto results in os command injection. The attack may be initiated remotely. The exploit is now public 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 confidenceA critical command injection vulnerability exists in Totolink A7100RU router firmware 7.4cu.2313_b20191024. The setNetworkCfg function in the CGI handler (/cgi-bin/cstecgi.cgi) fails to sanitize the 'proto' argument, allowing remote attackers to execute arbitrary OS commands via crafted HTTP requests.
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 checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelAccess the router's web interface or check the device label/marketing materials to confirm the model is Totolink A7100RUAffected if The device is NOT a Totolink A7100RU router - this vulnerability only affects that specific model
-
Check the installed firmware versionLog into the router web interface (typically 192.168.0.1 or 192.168.1.1) and navigate to System Status or Firmware Upgrade page to view the firmware version. Alternatively, check via telnet/SSH if enabled: cat /proc/version or cat /etc/versionAffected if The firmware version matches 7.4cu.2313_b20191024 or is an earlier version of the same release branch (7.4cu series)
-
Verify the CGI web interface is accessibleAttempt to access http://<router-ip>/cgi-bin/cstecgi.cgi from a browser or via curl. A valid response (even an error) indicates the CGI handler is active.Affected if The CGI endpoint responds - this confirms the web interface is enabled and reachable
-
Confirm remote web management access is enabledCheck router settings under 'Remote Management' or 'Access Control' to see if remote (WAN) access to the web interface is permitted. Look for settings like 'Enable Remote Management' or 'Allow WAN Access'.Affected if Remote web management access is enabled - this makes the device potentially exploitable from outside the local network
You are affected if you have a Totolink A7100RU router running firmware version 7.4cu.2313_b20191024 (or earlier in that series) with the web interface accessible, especially if remote management is enabled.
Generated from the published advisory. Verify against your own configuration.
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 dataApply vendor firmware update when available; if no patch exists, isolate the device behind a firewall or disable remote web management access.
- Consultation4.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2026-6114 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-6114 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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