CVE-2026-5976
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 security flaw has been discovered in Totolink A7100RU 7.4cu.2313_b20191024. This affects the function setStorageCfg of the file /cgi-bin/cstecgi.cgi of the component CGI Handler. Performing a manipulation of the argument sambaEnabled results in os command injection. It is possible to initiate the attack remotely. The exploit has been released to the public and may be used for attacks.
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 allows remote attackers to execute arbitrary operating system commands via the sambaEnabled parameter passed to the setStorageCfg function in the CGI handler at /cgi-bin/cstecgi.cgi.
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.
-
Confirm device model is Totolink A7100RUAccess the router web interface and check the status or system info page for the model number, or check the device label/markingAffected if The device is NOT a Totolink A7100RU router (different models are not affected by this specific CVE)
-
Verify web management interface is accessibleAttempt to access the router web interface via HTTP/HTTPS (typically ports 80 or 443 on the router's LAN or WAN IP address)Affected if The cstecgi.cgi endpoint is not reachable (the vulnerability requires the web interface to be accessible)
-
Check if storage/Samba configuration is exposedAccess the router web interface and navigate to the storage or Samba sharing settings section, or attempt a request to cstecgi.cgi with the setStorageCfg actionAffected if The storage/Samba configuration feature is not present or not accessible in the web interface
-
Determine if remote web management is enabledCheck the router admin panel for 'remote management', 'web access from WAN', or similar settings that control whether the web interface is accessible from the internetAffected if Remote management from WAN is enabled, exposing the web interface to external attackers
You are affected if you have a Totolink A7100RU router with its web interface (cstecgi.cgi) accessible externally and the Samba/storage feature enabled, allowing command injection via the unsanitized sambaEnabled parameter in the setStorageCfg function.
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 dataThis is an end-of-life device (2019 firmware) with no vendor patch available; replace with a currently supported router. If immediate replacement is infeasible, restrict network access to the CGI interface via firewall rules or disable remote administration to limit attack surface.
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-5976 — 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-5976 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