CVE-2026-5975
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. The impacted element is the function setDmzCfg of the file /cgi-bin/cstecgi.cgi of the component CGI Handler. Such manipulation of the argument wanIdx leads to os command injection. The attack may be performed from remote. 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 setDmzCfg function in /cgi-bin/cstecgi.cgi fails to sanitize the wanIdx parameter before passing it to system shell commands, allowing unauthenticated remote attackers to execute arbitrary OS commands.
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 web interface or check the device label to confirm it is a Totolink A7100RU routerAffected if The device is not a Totolink A7100RU model
-
Check the firmware versionLog into the router web interface and navigate to the status or system information page to find the firmware version, or use the command: cat /proc/version if you have shell accessAffected if The firmware version is 7.4cu.2313_b20191024 or earlier
-
Verify the vulnerable CGI binary existsIf you have shell access, check for the existence of /cgi-bin/cstecgi.cgi by running: ls -la /cgi-bin/cstecgi.cgiAffected if The file /cgi-bin/cstecgi.cgi does not exist or is not accessible
-
Check if the DMZ configuration interface is exposedAccess the router web interface and verify if the DMZ settings page is accessible at the default administration URL, typically http://<router-ip>/cgi-bin/cstecgi.cgiAffected if The DMZ configuration interface is accessible without additional network restrictions
-
Verify network exposure of the management interfaceCheck if the router web interface (port 80/443) is exposed to the internet by scanning external interfaces: nmap -p 80,443 <router-external-ip>Affected if The router administration interface is reachable from untrusted networks such as the internet
You are affected if you have a Totolink A7100RU router running firmware version 7.4cu.2313_b20191024 with the web interface accessible to attackers.
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 when available. Until then, disable remote administration interfaces, restrict network access to the device, and monitor for indicators of compromise. Consider network segmentation to limit exposure.
- Consultation6.0 h
- Implementation2.0 h
- Testing4.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 $4,032.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-5975 — 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-5975 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