CVE-2026-9475
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 determined in Totolink A8000RU 7.1cu.643_b20200521. This affects the function setIpQosRules of the file /cgi-bin/cstecgi.cgi of the component Web Management Interface. This manipulation of the argument Comment causes os command injection. Remote exploitation of the attack is possible. The exploit has been publicly disclosed and may be utilized.
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 A8000RU router's web management interface (cstecgi.cgi). The setIpQosRules function fails to sanitize the Comment parameter before passing it to system commands, allowing remote authenticated 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 router modelAccess the router's web management interface and check the device info/status page, or check the device label/marketing for the model name. Alternatively, inspect HTTP headers or check for Totolink-specific branding in the interface.Affected if The device is not a Totolink A8000RU router.
-
Check the installed firmware versionLog into the router web interface and navigate to System or Status settings to view the firmware version. If SSH/Telnet is enabled, run 'cat /proc/version' or check /etc/version file if accessible.Affected if The firmware version is 7.1cu.643_b20200521 or earlier (any version prior to a patched release).
-
Verify the CGI interface is accessibleAttempt to reach http://<router-ip>/cgi-bin/cstecgi.cgi via HTTP or HTTPS. A valid response indicates the web interface is active.Affected if The cstecgi.cgi endpoint responds, indicating the vulnerable interface is exposed.
-
Confirm QoS functionality is presentCheck the router web interface for IP QoS, Traffic Control, or Bandwidth Control settings. Look for a feature named setIpQosRules or similar QoS rule configuration.Affected if QoS or traffic shaping features are enabled or accessible in the management interface.
You are affected if the device is a Totolink A8000RU running firmware 7.1cu.643_b20200521 or earlier, with the web management interface (cstecgi.cgi) accessible and the setIpQosRules QoS feature present.
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 dataDisable remote web management access immediately; restrict management interface to trusted networks only. Contact Totolink for firmware updates or consider replacing the device if no patch is available.
- Consultation4.0 h
- Implementation8.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 $4,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-9475 — 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-9475 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