dbcve.org
Command InjectionWeakness · CWE-77

CVE-2026-7037

CRITICAL · 9.8 CVSS v3.1 Published 2026-04-26
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 security flaw has been discovered in Totolink A8000RU 7.1cu.643_b20200521. This issue affects the function setVpnPassCfg of the file /cgi-bin/cstecgi.cgi of the component CGI Handler. The manipulation of the argument pptpPassThru results in os command injection. The attack can be executed remotely. The exploit has been released to the public and may be used for attacks.

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 firmware (cgi-bin/cstecgi.cgi) allows remote attackers to execute arbitrary commands via the pptpPassThru argument in the setVpnPassCfg function without proper input sanitization.

MitigationApply vendor firmware patch if available; otherwise, restrict network access to the device's web interface, disable VPN/PPTP functionality if not required, and monitor for indicators of compromise.

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 is a Totolink A8000RU
    Access the router web interface or check the device label/metadata. The vulnerability specifically affects the A8000RU model.
    Affected if Device model is Totolink A8000RU and running unpatched firmware
  2. Verify the CGI binary is present
    Attempt to access or probe http://<router-ip>/cgi-bin/cstecgi.cgi via HTTP POST. The vulnerability exists in this binary in the setVpnPassCfg function.
    Affected if The cgi-bin/cstecgi.cgi endpoint responds to requests (indicates the vulnerable web interface is active)
  3. Check if VPN/PPTP functionality is enabled
    Navigate to the router web UI VPN or PPTP settings page. The vulnerability is triggered via the pptpPassThru parameter in setVpnPassCfg.
    Affected if PPTP VPN functionality is enabled or configurable on the device
  4. Identify firmware version
    Check the router admin panel for firmware version information, typically under System or Administration settings. Compare against any vendor patch releases.
    Affected if Firmware version is older than the patched version (if a patch has been released)

User is affected if they have a Totolink A8000RU router with the vulnerable cgi-bin/cstecgi.cgi interface exposed and PPTP VPN functionality enabled or accessible.

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 if available; otherwise, restrict network access to the device's web interface, disable VPN/PPTP functionality if not required, and monitor for indicators of compromise.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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