CVE-2026-9511
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 CA750-PoE 6.2c.510. This affects the function setWebWlanIdx of the file /cgi-bin/cstecgi.cgi of the component Setting Handler. Such manipulation of the argument webWlanIdx 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 · moderate confidenceOS command injection vulnerability in Totolink CA750-PoE router's web interface CGI script (/cgi-bin/cstecgi.cgi). The setWebWlanIdx function fails to sanitize the webWlanIdx parameter before passing it to system commands, allowing remote attackers to execute arbitrary OS commands on the device.
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 device's web administration interface or check the device label/marketing materials to confirm the model is Totolink CA750-PoEAffected if The device is not a Totolink CA750-PoE model (different models may have different vulnerabilities)
-
Check the firmware versionLog into the device web interface and navigate to the System Status or Firmware Upgrade page to view the current firmware version, or use the command 'cat /etc/version' or 'cat /proc/firmware_info' via telnet/ssh if availableAffected if The firmware version is 6.2c.510 exactly, or falls within an earlier version range of the 6.2c branch (e.g., 6.2c.x for x < 510)
-
Verify the vulnerable CGI script existsAttempt to access the URL 'http://<device_ip>/cgi-bin/cstecgi.cgi' using a GET or POST request to confirm the endpoint is reachable and respondsAffected if The cstecgi.cgi script is not found or returns a 404 error (the device may use a different firmware version or the script may have been renamed)
-
Check if remote administration is enabledIn the device web interface, navigate to the Remote Management or Administration settings to see if remote HTTP/HTTPS access from WAN is permittedAffected if Remote administration is enabled and the web interface is accessible from the WAN (internet-facing), allowing unauthenticated attackers to reach the vulnerable CGI endpoint
You are affected if you have a Totolink CA750-PoE device running firmware version 6.2c.510 or earlier, with the web management interface and CGI endpoint exposed to an untrusted network.
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 dataRestrict network access to the router's web interface, apply vendor firmware patch when available, or implement web application firewall rules to filter malicious input patterns in the webWlanIdx parameter.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-9511 — 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-9511 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