dbcve.org
Command InjectionWeakness · CWE-77

CVE-2026-9512

MEDIUM · 6.3 CVSS v3.1 Published 2026-05-25
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 flaw has been discovered in Totolink CA750-PoE 6.2c.510. This vulnerability affects the function setPasswordCfg of the file /cgi-bin/cstecgi.cgi of the component Setting Handler. Performing a manipulation of the argument admuser/admpass results in os command injection. The attack can be initiated remotely. The exploit has been released to the public and may be used for attacks.

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 device firmware 6.2c.510. The setPasswordCfg function in /cgi-bin/cstecgi.cgi accepts user-controlled admuser and admpass parameters that are unsafely passed to system shell commands, allowing remote attackers to execute arbitrary OS commands.

MitigationApply vendor firmware patch when available; until then, restrict network access to the device's web interface, disable remote administration if possible, and monitor for indicators of compromise.

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 device web interface or check device label/marketing to confirm it is a Totolink CA750-PoE device
    Affected if Device is not a Totolink CA750-PoE (different model or manufacturer)
  2. Check firmware version
    Log into the device web interface and navigate to the system status or firmware version page, or use the command 'cat /proc/version' or 'ver' via telnet/SSH if available
    Affected if Firmware version is 6.2c.510 or earlier (the vulnerable version)
  3. Verify web interface is accessible
    Attempt to access http://[device-ip]/cgi-bin/cstecgi.cgi from a browser or curl command
    Affected if The cgi-bin/cstecgi.cgi endpoint responds (device web interface is enabled and reachable)
  4. Confirm setPasswordCfg function exists
    Send a POST request to /cgi-bin/cstecgi.cgi with a test payload for the admuser parameter (e.g., admuser=';ls;') and observe if command execution occurs
    Affected if The device executes arbitrary commands injected into admuser or admpass parameters (vulnerable to command injection)

The device is affected if it is a Totolink CA750-PoE running firmware version 6.2c.510 or earlier and the web interface is accessible, allowing command injection via the setPasswordCfg function in cstecgi.cgi.

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 when available; until then, restrict network access to the device's web interface, disable remote administration if possible, and monitor for indicators of compromise.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,300
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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