dbcve.org
Command InjectionWeakness · CWE-77

CVE-2026-7123

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 was found in Totolink A8000RU 7.1cu.643_b20200521. Affected is the function setIptvCfg of the file /cgi-bin/cstecgi.cgi of the component CGI Handler. Performing a manipulation of the argument setIptvCfg results in os command injection. The attack can be initiated 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 CGI handler. The setIptvCfg function in /cgi-bin/cstecgi.cgi accepts unsanitized user input that gets passed to system shell commands, allowing remote attackers to execute arbitrary OS commands with root privileges.

MitigationApply vendor firmware patch if available; otherwise isolate affected devices behind a firewall or disable remote management. Consider replacing device if no patch 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 admin interface or check the device label/marketing materials to confirm the exact model is Totolink A8000RU
    Affected if Device is not a Totolink A8000RU unit
  2. Confirm CGI endpoint exists
    Attempt to access http://<router-ip>/cgi-bin/cstecgi.cgi via HTTP or HTTPS. A valid response (even an error) indicates the CGI handler is present
    Affected if The CGI endpoint returns a response (vulnerable code path may be present)
  3. Check if remote management is enabled
    Log into the router admin panel and look for 'Remote Management', 'Remote Access', or similar settings under System or Administration menus. Determine if access from WAN/internet is permitted
    Affected if Remote management or WAN access to the web interface is enabled
  4. Inspect for signs of command injection
    Check router system logs for suspicious commands, unexpected processes, or new user accounts. Look for unfamiliar entries in /etc/passwd or /etc/shadow if shell access is available
    Affected if Unexpected commands, scripts, or unauthorized accounts are found in logs or system files
  5. Verify firmware version
    Check the router's admin interface under 'Firmware Version', 'Status', or 'System Information' page for the installed firmware build date and version string
    Affected if Firmware is older than any vendor patch date (no patch date provided; compare to current firmware on vendor website if available)

You are affected if you have a Totolink A8000RU router with the CGI interface exposed and remote management enabled, or if signs of unauthorized command execution are present in the system

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor firmware patch if available; otherwise isolate affected devices behind a firewall or disable remote management. Consider replacing device if no patch is forthcoming.

Recommended fix Moderate confidence

A8000RU firmware version newer than 7.1cu.643_b20200521 (check Totolink.net for latest release)

  1. 1. Visit the official Totolink support page at www.totolink.net and navigate to the A8000RU product support section
  2. 2. Check for available firmware updates newer than version 7.1cu.643_b20200521
  3. 3. Download the latest stable firmware release for the A8000RU router
  4. 4. Access the router's web administration interface (typically at 192.168.1.1)
  5. 5. Navigate to the Administration or System settings section
  6. 6. Locate the Firmware Upgrade or Update option
  7. 7. Upload and apply the new firmware version
  8. 8. After the upgrade completes, verify the router is functioning normally and confirm the new firmware version is installed
Caveat Firmware upgrades may reset router configuration to defaults; back up current settings before upgrading if possible

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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