Authenticated command execution via unsanitized FileName
Published May 26, 2026 · Updated May 26, 2026
OS command injection in TOTOLINK CA750-PoE 6.2c.510 allows remote authenticated users to execute arbitrary commands through FileName. The setUploadUserData handler in /cgi-bin/cstecgi.cgi passes the FileName value to command execution without neutralizing shell metacharacters. A valid SESSION_ID cookie is required, and successful exploitation runs commands with the appliance service's privileges.
Summary
What happened
OS command injection in TOTOLINK CA750-PoE 6.2c.510 allows remote authenticated users to execute arbitrary commands through FileName. The setUploadUserData handler in /cgi-bin/cstecgi.cgi passes the FileName value to command execution without neutralizing shell metacharacters. A valid SESSION_ID cookie is required, and successful exploitation runs commands with the appliance service's privileges.
The record
- CVE
- CVE-2026-9532
- Published
- May 26, 2026
- Updated
- May 26, 2026
- Vendor
- TOTOLINK
- Product
- CA750-PoE
- Classifications
- CWE-77, T1059.004
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 26, 2026CVE publishedPublication date reported by the CVE source.
- May 26, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=6.2c.510
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- CA750-PoE setUploadUserData command-injection PoCfunctional · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo