CVE-2025-34035
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 · uneditedAn 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.
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 · high confidenceOS command injection vulnerability in EnGenius EnShare Cloud Service version 1.4.11 and earlier. The usbinteract.cgi script fails to sanitize user input in the path parameter, allowing unauthenticated remote attackers to inject arbitrary shell commands that execute with root privileges, leading to full system compromise.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 1.1.0.28= 1.3.1.42= 1.4.0= 1.4.1.28= 1.4.2= 1.4.7= 1.4.9= 1.1.0.29= 1.3.1.41= 1.4.0= 1.4.2= 1.4.5= 1.4.9= 1.4.11= 1.1.0.50= 1.2.1.46= 1.3.1.63= 1.4.0.23= 1.4.1= 1.4.2= 1.4.3= 1.4.5= 1.4.9= 1.4.11= 1.1.0= 1.2.2.23= 1.3.0= 1.3.1.26= 1.3.5.18= 1.4.0= 1.4.3= 1.4.5= 1.1.0= 1.3.1.34= 1.4.1= 1.4.3= 1.4.5= 1.1.0= 1.2.2.27= 1.3.0= 1.3.1.34= 1.4.0= 1.4.1= 1.4.3= 1.4.5= 1.2.0= 1.3.0= 1.3.2= 1.3.3= 1.3.3.17= 1.3.7.20= 1.3.9.21CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Identify EnShare Cloud Service firmware versionAccess the device admin interface or check the firmware version through the device status page, typically found under System > Status or similar. The firmware version is usually displayed on the main dashboard or in a Firmware/Version information section.Affected if The firmware version is 1.4.11 or earlier, or matches any of the specific versions listed in the affected products list for your device model (Esr300, Esr350, Esr600, Esr900, Esr1200, Esr1750, or Epg5000).
-
Confirm device model is vulnerableIdentify the exact model number of the EnGenius device through the admin interface (typically under System > Status or Device Information). Match the model against the affected products list.Affected if The device is an Esr300, Esr350, Esr600, Esr900, Esr1200, Esr1750, or Epg5000 with a firmware version matching those listed in the affected versions.
-
Check for usbinteract.cgi accessibilityAttempt to access the CGI script via HTTP/HTTPS request to the EnShare web interface. The typical path would be something like http://[device-ip]/cgi-bin/usbinteract.cgi or similar paths under the EnShare service.Affected if The usbinteract.cgi script is accessible and responds to requests, indicating the EnShare web interface is active.
-
Verify EnShare service is exposed to networkCheck if the EnShare management interface is reachable from untrusted networks. This can be done by attempting to access the device IP from an external network or reviewing firewall rules and port forwarding configurations.Affected if The EnShare service (typically ports 80 or 443, or custom ports configured for EnShare) is accessible from outside the local network without firewall restrictions.
A device is affected if it runs EnShare Cloud Service firmware version 1.4.11 or earlier on a vulnerable model (Esr300, Esr350, Esr600, Esr900, Esr1200, Esr1750, or Epg5000), with the usbinteract.cgi script accessible over the network.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade EnShare Cloud Service to a version newer than 1.4.11; if no patch is available, disable the usbinteract.cgi service or restrict network access to the management interface until a vendor fix is released.
- Consultation4.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,440.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-34035 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-34035 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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