CVE-2026-7204
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 · uneditedA vulnerability was determined in Totolink A8000RU 7.1cu.643_b20200521. This issue affects the function setPptpServerCfg of the file /cgi-bin/cstecgi.cgi of the component CGI Handler. This manipulation of the argument enable causes os command injection. The attack may be initiated remotely. The exploit has been publicly disclosed and may be utilized.
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 confidenceOS command injection vulnerability in Totolink A8000RU router firmware (cstecgi.cgi). The setPptpServerCfg function fails to sanitize the 'enable' parameter, allowing remote attackers to inject arbitrary OS commands via the CGI interface. This yields full device compromise with root privileges.
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 checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelAccess the router's web interface or check the HTTP response headers/HTML for 'Totolink A8000RU' or similar branding. You can also check the DHCP fingerprint or SNMP if available.Affected if The device is a Totolink A8000RU router.
-
Confirm the CGI handler existsCheck if cstecgi.cgi is accessible by attempting a GET request to http://<router-ip>/cstecgi.cgi. Look for a valid HTTP response (200 or similar) rather than a 404.Affected if The cstecgi.cgi file exists and responds to requests.
-
Check if PPTP server function is accessibleSend a POST request to cstecgi.cgi with the action parameter set to 'setPptpServerCfg' and observe the response. For example: POST /cstecgi.cgi with 'action=setPptpServerCfg' in the body.Affected if The CGI accepts the setPptpServerCfg action without requiring authentication.
-
Verify the enable parameter is processedSend a POST request with a benign test value for the 'enable' parameter (such as 'enable=0' to disable PPTP) and check if the configuration changes are applied or reflected in the response.Affected if The 'enable' parameter is accepted and processed by the CGI handler without input sanitization validation.
If the device is a Totolink A8000RU with an accessible cstecgi.cgi that accepts the setPptpServerCfg action and processes the 'enable' parameter without authentication, the environment is affected by this CVE.
Generated from the published advisory. Verify against your own configuration.
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 dataApply vendor firmware patch immediately; if unavailable, disable remote administration interfaces and segment device from untrusted networks. CVSS 9.8 indicates critical exposure requiring urgent remediation.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-7204 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-7204 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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