dbcve.org
Command InjectionWeakness · CWE-77

CVE-2026-7122

CRITICAL · 9.8 CVSS v3.1 Published 2026-04-27
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 has been found in Totolink A8000RU 7.1cu.643_b20200521. This impacts the function setUPnPCfg of the file /cgi-bin/cstecgi.cgi of the component CGI Handler. Such manipulation of the argument enable leads to os command injection. It is possible to launch the attack remotely. The exploit has been disclosed to the 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 · moderate confidence

OS command injection vulnerability in Totolink A8000RU router's CGI handler (/cgi-bin/cstecgi.cgi). The setUPnPCfg function fails to properly sanitize the 'enable' parameter, allowing remote attackers to inject and execute arbitrary operating system commands on the affected device.

MitigationRestrict network access to the device's management interface immediately. Monitor for indicators of compromise. Contact Totolink for available firmware patches or consider device replacement if no update is forthcoming.

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. Identify device model
    Access the router's web interface or check HTTP headers/server responses to confirm the device is a Totolink A8000RU. You can also check via SSH or telnet if enabled, or inspect DHCP/ARP tables for the device hostname.
    Affected if The device model is Totolink A8000RU and the firmware has not been patched.
  2. Verify CGI endpoint accessibility
    Attempt to access or curl http://<device-ip>/cgi-bin/cstecgi.cgi and confirm the endpoint responds. Check if the CGI handler is enabled and reachable.
    Affected if The /cgi-bin/cstecgi.cgi endpoint is accessible and responds to requests.
  3. Confirm UPnP configuration function exists
    Send a request to the CGI endpoint with a JSON payload targeting the setUPnPCfg function (e.g., {"topicurl":"setUPnPCfg","enable":"test"}) and observe the response. Alternatively, check if UPnP is enabled in the router's web interface under advanced settings.
    Affected if The setUPnPCfg function is present and the 'enable' parameter is processed without proper sanitization.
  4. Check management interface exposure
    Determine if the router's web management interface (port 80/443) is exposed to the internet or untrusted networks. Review firewall rules, port forwards, and WAN accessibility.
    Affected if The router's management interface is accessible from untrusted networks without VPN or IP restriction.
  5. Compare firmware version
    Check the router's web interface for the firmware version under System or Status settings. Compare against any available Totolink firmware releases for the A8000RU.
    Affected if The firmware version is older than the patched version that addresses CVE-2026-7122.

You are affected if you have a Totolink A8000RU router where the CGI endpoint /cgi-bin/cstecgi.cgi is accessible and the setUPnPCfg function processes the 'enable' parameter without sanitization, particularly if the management interface is exposed to untrusted networks.

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

Restrict network access to the device's management interface immediately. Monitor for indicators of compromise. Contact Totolink for available firmware patches or consider device replacement if no update is forthcoming.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-7122 — 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-7122 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