CVE-2025-14704
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 · uneditedA vulnerability was found in Shiguangwu sgwbox N3 2.0.25. The impacted element is an unknown function of the file /eshell of the component API. The manipulation results in path traversal. It is possible to launch the attack remotely. The exploit has been made public and could be used. The vendor was contacted early about this disclosure but did not respond in any way.
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 confidenceA path traversal vulnerability exists in the /eshell API endpoint of Shiguangwu sgwbox N3 version 2.0.25. An attacker can manipulate the API to access files outside the intended directory by using '../' sequences in the file parameter, potentially reading sensitive system files.
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<= 2.0.25CVSS 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 sgwbox N3 firmware versionAccess the device administration interface or check system information page to determine the installed firmware version. This is typically found in Settings > System > Version or similar administrative panel location.Affected if The firmware version displayed is 2.0.25 or any version lower than 2.0.25 (e.g., 2.0.24, 2.0.20, etc.)
-
Verify /eshell API endpoint presenceAttempt to access the /eshell endpoint via HTTP request (e.g., GET http://<device-ip>/eshell or similar path based on the product's API structure). Check if the endpoint responds or is accessible.Affected if The /eshell API endpoint returns any response (success or error), indicating it is exposed and potentially vulnerable.
-
Check network exposure of /eshell endpointReview firewall rules, access control lists, or network segmentation configurations to determine if the /eshell endpoint is accessible from untrusted networks or the internet.Affected if The /eshell endpoint is reachable from external networks or untrusted zones without proper access restrictions.
-
Inspect API parameter handling for path traversal protectionReview any available API documentation, proxy logs, or web application firewall (WAF) logs to examine how the /eshell endpoint handles file parameter inputs containing '../' sequences.Affected if The endpoint does not sanitize or reject path traversal sequences ('../') in the file parameter, allowing arbitrary file access.
A user is affected if their sgwbox N3 firmware is version 2.0.25 or lower AND the /eshell API endpoint is accessible, as the path traversal vulnerability can be exploited to read files outside the intended directory.
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 dataImplement strict input validation on the /eshell API endpoint to restrict file paths to allowed directories. Use canonicalization and whitelist approaches to prevent path traversal attacks.
- Consultation3.0 h
- Implementation4.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-14704 — 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-14704 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