CVE-2026-5993
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 identified in Totolink A7100RU 7.4cu.2313_b20191024. This vulnerability affects the function setWiFiGuestCfg of the file /cgi-bin/cstecgi.cgi of the component CGI Handler. Such manipulation of the argument wifiOff leads to os command injection. The attack can be executed remotely. The exploit is publicly available and might 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 confidenceOS command injection vulnerability in Totolink A7100RU router firmware 7.4cu.2313_b20191024. The setWiFiGuestCfg function in /cgi-bin/cstecbi.cgi improperly handles user-supplied input passed via the wifiOff parameter, allowing attackers to inject arbitrary operating system commands remotely.
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 device modelAccess the router web interface or check the device label/marketing to confirm the model is Totolink A7100RUAffected if Device is not a Totolink A7100RU router - different models are not affected by this specific CVE
-
Check firmware versionLog into the router web interface and navigate to System Status or Firmware Upgrade page to view the installed firmware version, or check via telnet/SSH if availableAffected if Firmware version is 7.4cu.2313_b20191024 (the known affected version); versions other than this are not confirmed vulnerable unless the vendor indicates otherwise
-
Verify web interface accessibilityAttempt to access the router web interface over HTTP/HTTPS on the local network (typically ports 80 or 443)Affected if The web interface at /cgi-bin/cstecbi.cgi is reachable from the network - the vulnerability requires this CGI endpoint to be accessible
-
Check WiFi guest feature availabilityLocate the WiFi guest network settings in the router web interface under Wireless or WiFi settings sectionAffected if The WiFi guest network configuration feature is present and accessible - the vulnerability exists in the setWiFiGuestCfg function handling the wifiOff parameter
You are affected if you have a Totolink A7100RU router running firmware version 7.4cu.2313_b20191024 with the web interface and WiFi guest configuration feature accessible.
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 patch if available; if no patch exists, restrict network access to the router's web interface via firewall rules or network segmentation, and consider replacing the device with a supported model.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-5993 — 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-5993 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