dbcve.org
N3 FirmwareOperating system · Sgwbox

CVE-2025-14709

CRITICAL · 9.8 CVSS v3.1 Published 2025-12-15
Fix available
A fix is available. Upgrade to after 2.0.25 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

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 · unedited
A security vulnerability has been detected in Shiguangwu sgwbox N3 2.0.25. Affected by this issue is some unknown functionality of the file /usr/sbin/http_eshell_server of the component WIRELESSCFGGET Interface. The manipulation of the argument params leads to buffer overflow. Remote exploitation of the attack is possible. The exploit has been disclosed publicly and may 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 · high confidence

A buffer overflow vulnerability in the WIRELESSCFGGET interface of Shiguangwu sgwbox N3 version 2.0.25 allows remote attackers to overflow the 'params' argument in the /usr/sbin/http_eshell_server binary. This critical flaw (CVSS 9.8) can be exploited remotely without authentication, and a public exploit is already available.

MitigationSince the vendor has not responded to early disclosure, organizations should immediately restrict network access to the affected device's management interface, implement network segmentation, and monitor for exploitation attempts until a vendor patch becomes available or consider replacing the device.

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
N3 FirmwareOperating system
Affected:<= 2.0.25

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device model
    Check the device label, web interface, or SSH banner for 'sgwbox N3' or 'Shiguangwu' branding. Firmware version may also be visible in the admin panel (often under System > Firmware or Status).
    Affected if The device is not a Shiguangwu sgwbox N3, then it is not affected.
  2. Determine the firmware version
    Access the device's web management interface or check via CLI (e.g., 'cat /etc/version' or 'fw_printenv' if available). Compare the version number to 2.0.25.
    Affected if Firmware version is 2.0.25 or lower, the device is within the affected range.
  3. Verify http_eshell_server binary exists
    If you have CLI access (SSH/Telnet), run 'ls -la /usr/sbin/http_eshell_server' to confirm the binary is present on the device.
    Affected if The binary exists, the vulnerable component is installed.
  4. Confirm the WIRELESSCFGGET interface is accessible
    Attempt to access the WIRELESSCFGGET endpoint via HTTP/HTTPS request to the device (e.g., curl http://<device-ip>/WIRELESSCFGGET?params=test). A response (even an error) indicates the interface is exposed.
    Affected if The interface responds, it is reachable and the attack surface is present.
  5. Check network exposure of management interface
    Review firewall rules, NAT configuration, or ACLs to determine if the device's web interface (port 80/443) is accessible from untrusted networks or the internet.
    Affected if The management interface is exposed to the internet or untrusted networks, the device is remotely exploitable without authentication.

The device is affected if it is a Shiguangwu sgwbox N3 running firmware version 2.0.25 or lower, with the http_eshell_server binary present and its management interface network-accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 2.0.25
Interim mitigation

Since the vendor has not responded to early disclosure, organizations should immediately restrict network access to the affected device's management interface, implement network segmentation, and monitor for exploitation attempts until a vendor patch becomes available or consider replacing the device.

Fix this in N3 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-14709 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-14709 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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