CVE-2026-7718
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 identified in Totolink WA300 5.2cu.7112_B20190227. Impacted is the function setWebWlanIdx of the file /cgi-bin/cstecgi.cgi of the component POST Request Handler. The manipulation of the argument webWlanIdx leads to command injection. The attack may be initiated 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 confidenceCommand injection vulnerability in Totolink WA300 router firmware (version 5.2cu.7112_B20190227). The setWebWlanIdx function in /cgi-bin/cstecgi.cgi fails to sanitize the webWlanIdx parameter, allowing remote attackers to inject and execute arbitrary OS commands via crafted POST requests.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
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 web interface or check the device label. Look for 'Totolink WA300' branding or check the administration page for device information.Affected if The device is not a Totolink WA300 router
-
Check the firmware versionLog into the router web interface and navigate to System Status or Firmware Upgrade page. The version should be displayed as '5.2cu.7112_B20190227' or similar.Affected if The firmware version is 5.2cu.7112_B20190227 exactly, or within a similar 5.2cu.7112 series (the exact range is unknown but this specific version is confirmed vulnerable)
-
Verify the CGI binary existsAttempt to access or probe the endpoint /cgi-bin/cstecgi.cgi via HTTP/HTTPS to confirm it is present on the device.Affected if The /cgi-bin/cstecgi.cgi endpoint responds or is accessible from the network
-
Confirm web management interface is enabledCheck if the router's web interface (HTTP/HTTPS on ports 80/443) is listening and accessible from the network where the attacker would send the malicious POST request.Affected if The web management interface is exposed and accessible (the CGI endpoint must be reachable for exploitation)
The device is affected if it is a Totolink WA300 router running firmware version 5.2cu.7112_B20190227 (or similar 5.2cu.7112 series) with the web interface and /cgi-bin/cstecgi.cgi endpoint accessible to the attacker.
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-supplied firmware patch when available; alternatively, disable the web management interface or restrict network access to trusted IPs to reduce attack surface.
- Consultation4.0 h
- Implementation6.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 $4,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-7718 — 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-7718 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