dbcve.org
Command InjectionWeakness · CWE-77

CVE-2026-9384

CRITICAL · 9.8 CVSS v3.1 Published 2026-05-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
A vulnerability was found in Totolink A8000RU 7.1cu.643_b20200521. This vulnerability affects the function setDiagnosisCfg of the file /cgi-bin/cstecgi.cgi of the component Web Management Interface. The manipulation of the argument ip results in os command injection. The attack can be executed remotely. The exploit has been made public and could 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 confidence

OS command injection vulnerability in Totolink A8000RU router's web management interface (cstecgi.cgi). The setDiagnosisCfg function fails to sanitize the 'ip' parameter, allowing remote attackers to execute arbitrary OS commands without authentication. CVSS 9.8 indicates trivial exploitability over the network.

MitigationApply vendor firmware patch when available; if no patch (device appears end-of-life given 2020 firmware), replace the device or restrict web management interface to trusted networks only via firewall rules.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm device model is Totolink A8000RU
    Access the router web management interface and check the device model information, typically found on the status page or in the device info section. Alternatively, check physical device labeling or use network discovery tools to identify the device manufacturer and model.
    Affected if The device is not a Totolink A8000RU router - the vulnerability only affects this specific model.
  2. Verify web management interface is accessible
    Attempt to access the router's web interface by navigating to its IP address (typically 192.168.0.1 or 192.168.1.1) over HTTP/HTTPS ports 80 or 443. Confirm the interface responds and presents a login page.
    Affected if The web management interface is not accessible at all - the command injection requires interaction with this interface.
  3. Confirm the vulnerable CGI endpoint exists
    Check if the /cgi-bin/cstecgi.cgi endpoint is present and accessible on the device by making an HTTP request to http://[router-ip]/cgi-bin/cstecgi.cgi
    Affected if The cstecgi.cgi script is not present - the setDiagnosisCfg function that contains the vulnerability is part of this script.
  4. Determine if remote administration is enabled
    In the router web interface, navigate to the administrative or system settings and check whether remote management/access from WAN is enabled. This is often found under 'Remote Management', 'Admin Access', or 'WAN Access' settings.
    Affected if Remote administration from external networks is enabled - this allows unauthenticated or authenticated attackers from the internet to reach the vulnerable endpoint.
  5. Compare installed firmware version to affected releases
    In the router web interface, locate the firmware version information (usually under 'System Status', 'Firmware Version', or 'About' section). Note that no specific version ranges were provided in the CVE, so compare against any Totolink firmware release notes or security advisories for this model.
    Affected if The firmware version is older than patched releases or falls within any known affected version range.

You are affected if you have a Totolink A8000RU router with an accessible web management interface where remote WAN administration is enabled, and the cstecgi.cgi endpoint is present on the device.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor firmware patch when available; if no patch (device appears end-of-life given 2020 firmware), replace the device or restrict web management interface to trusted networks only via firewall rules.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-9384 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-9384 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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