Root command execution via system.setclock injection
Published Jul 31, 2026 · Updated Jul 31, 2026
OS command injection in Cudy TR1200 2.4.15 and TR3000 2.4.21 allows remote authenticated users to execute commands as root. The CVE record identifies system.setclock but does not disclose the crafted field or command-building operation that fails to neutralize it. Administrative network access is required; Cudy separately describes insufficient parameter validation in the TR3000 IPv6 settings page, so that detail is not established for TR1200.
Summary
What happened
OS command injection in Cudy TR1200 2.4.15 and TR3000 2.4.21 allows remote authenticated users to execute commands as root. The CVE record identifies system.setclock but does not disclose the crafted field or command-building operation that fails to neutralize it. Administrative network access is required; Cudy separately describes insufficient parameter validation in the TR3000 IPv6 settings page, so that detail is not established for TR1200.
The record
- CVE
- CVE-2026-38710
- Published
- Jul 31, 2026
- Updated
- Jul 31, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-77, T1059
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Jul 31, 2026CVE publishedPublication date reported by the CVE source.
- Jul 31, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
No public exploit references are available in this record.
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