CVE-2026-9435
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 A8000RU 7.1cu.643_b20200521. The affected element is the function setQosCfg of the file /cgi-bin/cstecgi.cgi of the component Web Management Interface. Performing a manipulation of the argument enable results in os command injection. Remote exploitation of the attack is possible. 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 confidenceOS command injection vulnerability in Totolink A8000RU router's web management interface (cstecgi.cgi). The setQosCfg function fails to sanitize the 'enable' parameter before passing it to system calls, allowing 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 device modelAccess the router's web interface or check the device label/metadata to confirm the model is Totolink A8000RUAffected if Device is not a Totolink A8000RU model
-
Determine firmware versionLog into the router web interface and navigate to System Status or Firmware Upgrade section to display the current firmware version; alternatively, use SNMP or check via telnet/SSH if availableAffected if Firmware version is unpatched and falls within any vulnerable version range (compare against vendor release notes if available)
-
Verify cstecgi.cgi is accessibleAttempt to access http://<router-ip>/cstecgi.cgi via HTTP GET or POST request; a valid response indicates the CGI interface is exposedAffected if The cstecgi.cgi endpoint responds and is reachable from the network
-
Check if QoS feature is enabledLog into the router web interface and navigate to QoS or Bandwidth Control settings; inspect whether QoS is configured or the 'enable' parameter can be setAffected if QoS functionality is accessible or configurable through the web interface
-
Confirm remote web management is enabledCheck router settings under Administration, Remote Management, or Access Control to see if remote HTTP/HTTPS access to the web interface is permitted from external IPsAffected if Remote web management is enabled and the management interface is reachable from untrusted networks
A user is affected if they are running a Totolink A8000RU router with an unpatched firmware version, the cstecgi.cgi interface is accessible, and QoS feature can be manipulated through the 'enable' parameter.
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 dataUpgrade to patched firmware if available; otherwise replace the device. As an interim control, restrict access to the web management interface to trusted networks or disable remote management.
- Consultation2.0 h
- Implementation4.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-9435 — 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-9435 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