dbcve.org
Command InjectionWeakness · CWE-77

CVE-2026-9532

MEDIUM · 6.3 CVSS v3.1 Published 2026-05-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable 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 vulnerability has been detected in Totolink CA750-PoE 6.2c.510. The affected element is the function setUploadUserData of the file /cgi-bin/cstecgi.cgi of the component Setting Handler. Such manipulation of the argument FileName leads to os command injection. The attack may be performed from remote. The exploit has been disclosed publicly 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 confidence

OS command injection vulnerability in Totolink CA750-PoE router's web interface. The setUploadUserData function in /cgi-bin/cstecgi.cgi fails to sanitize the FileName parameter, allowing remote attackers to execute arbitrary OS commands on the device.

MitigationApply vendor firmware patch if available; otherwise restrict network access to the device's management interface and disable unused CGI functions to reduce attack surface.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify device model
    Access the router's web interface or check the device label/marketing to confirm the model is Totolink CA750-PoE
    Affected if The device is not a Totolink CA750-PoE router
  2. Locate firmware version
    Log into the router admin panel and navigate to System Status or Firmware Upgrade page to find the installed firmware version
    Affected if Unable to determine firmware version for comparison
  3. Verify vulnerable endpoint exists
    Check if the CGI script /cgi-bin/cstecgi.cgi is accessible by making an HTTP request to the router's web interface on port 80 or 443
    Affected if The cgi-bin/cstecgi.cgi endpoint returns a 404 or is unreachable
  4. Confirm setUploadUserData function is present
    Review the firmware binary or attempt to call the cgi-bin/cstecgi.cgi endpoint with a request targeting the setUploadUserData function (via the topic or action parameter)
    Affected if The setUploadUserData function is not found in the CGI binary or API
  5. Check network exposure
    Determine if the router's web administrative interface is directly accessible from the internet (WAN side) rather than only from a trusted LAN
    Affected if The web interface is exposed to untrusted networks

A user is affected if they own a Totolink CA750-PoE router with the web interface exposed and the vulnerable cgi-bin/cstecgi.cgi endpoint present, where the setUploadUserData function can be reached via the FileName parameter without authentication.

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 management interface and disable unused CGI functions to reduce attack surface.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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