CVE-2026-7202
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 has been found in Totolink A8000RU 7.1cu.643_b20200521. This affects the function setWiFiWpsStart of the file /cgi-bin/cstecgi.cgi of the component CGI Handler. The manipulation of the argument wscDisabled leads to os command injection. The attack can be initiated 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 confidenceOS command injection vulnerability in Totolink A8000RU router firmware (7.1cu.643_b20200521). The setWiFiWpsStart function in /cgi-bin/cstecgi.cgi fails to sanitize the wscDisabled parameter, allowing remote unauthenticated attackers to execute arbitrary operating system commands.
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 device label to confirm the model is Totolink A8000RU. Alternatively, use nmap or similar tool to perform HTTP service fingerprinting on the target IP.Affected if The device is a Totolink A8000RU router
-
Confirm firmware versionLog into the router web interface and navigate to the System or Status page to view the firmware version. If CLI access is available, check via telnet or SSH if enabled.Affected if The installed firmware version matches or falls within any known affected version ranges published for this CVE
-
Verify CGI endpoint accessibilitySend an HTTP POST request to http://<router_ip>/cgi-bin/cstecgi.cgi with a probe payload to confirm the endpoint is reachable and responds. Use: curl -X POST http://TARGET/cgi-bin/cstecgi.cgi -d '{"topicurl":"setWiFiWpsStart"}'Affected if The /cgi-bin/cstecgi.cgi endpoint responds to requests (indicating the web interface is exposed)
-
Check WPS configuration statusLog into the router web interface and navigate to the Wireless settings to verify if WPS (Wi-Fi Protected Setup) is enabled or if the related wscDisabled parameter can be modified.Affected if WPS functionality is enabled on the device, making the setWiFiWpsStart function active
-
Inspect for indicators of compromiseReview router system logs for suspicious commands or unexpected entries. Check for new user accounts, unknown processes, or unusual network connections originating from the device.Affected if Log entries show unauthorized command execution, unexpected CGI requests to cstecgi.cgi, or lateral network activity from the router
The device is affected if it is a Totolink A8000RU with a vulnerable firmware version, the CGI endpoint is accessible, and the WPS feature is enabled, potentially showing signs of unauthorized command execution in logs.
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 update if available; otherwise disable remote CGI access from WAN, segment affected devices, and consider device replacement. No official patch confirmed from provided description.
- Consultation4.0 h
- Testing3.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 $2,576.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-7202 — 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-7202 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