What it is
CVE-2025-34035 is an unauthenticated EnGenius EnShare IoT Gigabit Cloud Service Command Injection. An OS command injection vulnerability exists in EnGenius EnShare Cloud Service version 1.4.11 and earlier. The...
Vulnerability report
EnGenius EnShare IoT Gigabit Cloud Service Command Injection
EnGenius / EnShare IoT Gigabit Cloud Service · 0 to <= 1.4.11
Decision summary
Direct answers before the deeper technical record.
What it is
CVE-2025-34035 is an unauthenticated EnGenius EnShare IoT Gigabit Cloud Service Command Injection. An OS command injection vulnerability exists in EnGenius EnShare Cloud Service version 1.4.11 and earlier. The...
Is it exploited?
Yes. Previdian tracks this CVE as a known exploited vulnerability. Confidence is high. Also confirmed by third-party sources.
Who is affected?
EnGenius / EnShare IoT Gigabit Cloud Service 0 to <= 1.4.11.
What should we do?
Prioritize remediation. Validate affected assets and apply vendor fixes on an accelerated timeline.
Overview
An OS command injection vulnerability exists in EnGenius EnShare Cloud Service version 1.4.11 and earlier. The usbinteract.cgi script fails to properly sanitize user input passed to the path parameter, allowing unauthenticated remote attackers to inject arbitrary shell commands.
The injected commands are executed with root privileges, leading to full system compromise. Exploitation evidence was observed by the Shadowserver Foundation on 2024-12-05 UTC.
Exploitation evidence
Third-party attestation and first-party sensor observation are shown separately so teams can judge the evidence chain.
The Hacker News
A trusted third party reported exploitation.
Nuclei Templates
Public scanner or PoC coverage increases practical exploitability.
Per-source evidence links for KEV attestations are available through the Previdian Pro API.
Learn about Pro API access| Source | Added |
|---|---|
| The Hacker News First | 2026-10-05 15:37 UTC |
Detection
Make the evidence actionable in scanner, SOC, and edge-control workflows.
Request targets and User-Agents available in Pro. Callback host details available in Enterprise.
Nuclei template detected 01 Jun 2026.
View Nuclei template (opens in new tab)No Previdian virtual patch is currently available. Future rules ship for ModSecurity, Cloudflare, and AWS WAF.
Learn about virtual patches →Scanner and exploit-framework references linked to this CVE.
| Scanner | Reference | Detected |
|---|---|---|
| Nuclei | https://github.com/projectdiscovery/nuclei-templates/blob/main/http/cves/2025/CVE-2025-34035.yaml | 01 Jun 2026 |
Risk and context
CVSS v4.0
Potential damage if exploited. Separate from whether attackers are using it.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
EPSS
22.8%
Estimated chance of exploitation in the next 30 days. Previdian's warning comes from evidence, not this score.
Recent mention · The Hacker News
Ravie LakshmananOct 05, 2026Vulnerability / Malware Threat actors have been observed attempting to exploit a now-patched critical security flaw impacting the Realtek Jungle software development kit (SDK) to deploy a botnet malware called Cling. "Cling is notable not because...
Read full advisoryCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
These PoCs are unverified and could contain malware. Use at your own risk.
nuclei · Created Unknown
Timeline
15:37 UTC
High-confidence, third-party attested exploitation
14:21 UTC
Public proof-of-concept code published
15:34 UTC
Scanner coverage available
01:00 UTC
Vulnerability disclosed publicly
19:15 UTC
Identifier reserved by the CNA
Pro API
Confidence, exploit status, sensor telemetry, PoCs, scanner integrations, mentions, and tags are available programmatically for VM, SOC, and CTI workflows.
GET /api/v2/pro/kevs/CVE-2025-34035
Free JSON includes basic KEV fields{
"cve_id": "CVE-2025-34035",
"confidence": "High",
"cvss_score": 10.0,
"cvss_estimated": false,
"epss_score": 0.22811,
"exploit_status": {
"exploited_in_the_wild": true,
"active_exploitation_observed": false
},
"sensor_telemetry": { "attempts": 0, "sensors": 0 }
}