dbcve.org
Command InjectionWeakness · CWE-77

CVE-2026-6025

CRITICAL · 9.8 CVSS v3.1 Published 2026-04-10
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 identified in Totolink A7100RU 7.4cu.2313_b20191024. This affects the function setSyslogCfg 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 is publicly available and might 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 A7100RU router's CGI handler (cstecgi.cgi). The setSyslogCfg function improperly sanitizes the 'enable' argument, allowing attackers to inject arbitrary operating system commands via the web interface. The vulnerability is remotely exploitable without authentication.

MitigationApply vendor firmware update when available. If no update exists, implement network segmentation to isolate the device and consider replacing affected hardware. Disable remote administration interfaces if not required.

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 the device model
    Access the router's web interface or check the device label/marketing materials to confirm it is a Totolink A7100RU model. Alternatively, inspect HTTP responses or SNMP outputs for the device identifier.
    Affected if The device is confirmed to be a Totolink A7100RU router.
  2. Check the installed firmware version
    Log into the router's admin panel and navigate to the System or Status section to view the firmware version. If remote CLI access is available, use 'cat /proc/version' or the vendor-specific command to retrieve firmware information.
    Affected if The installed firmware version does not have the CVE patch applied (compare to any vendor-released updates for this model).
  3. Verify the CGI interface is accessible
    Attempt to access the cstecgi.cgi endpoint on the router's web interface (typically http://<router-ip>/cstecgi.cgi). Send a GET request and verify the endpoint responds.
    Affected if The cstecgi.cgi endpoint is reachable from the network.
  4. Confirm remote administration is enabled
    In the router's admin panel, check the 'Remote Management' or 'Remote Access' settings under the Administration or System menu. Verify whether remote access to the web interface is permitted from external IP addresses.
    Affected if Remote administration is enabled and the router's web interface is accessible from untrusted networks.
  5. Inspect the setSyslogCfg function behavior
    If you have access, examine the CGI binary or its configuration to confirm the setSyslogCfg function processes the 'enable' parameter without proper input sanitization. This may require firmware reverse engineering or examining the running CGI process.
    Affected if The 'enable' parameter in setSyslogCfg accepts and executes shell metacharacters without validation.

You are affected if you have a Totolink A7100RU router with unpatched firmware, the cstecgi.cgi interface is exposed, and remote administration is enabled, allowing unauthenticated command injection via the 'enable' parameter.

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 update when available. If no update exists, implement network segmentation to isolate the device and consider replacing affected hardware. Disable remote administration interfaces if not required.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,820
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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