CVE-2025-14704VulnerabilityPublished 15 Dec 2025

CVE-2025-14704: Shiguangwu sgwbox N3 · Path Traversal

Affects Shiguangwu sgwbox N3Source CVE Database V5

Not known to be exploited · 12% EPSS · CVSS 6.9 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score

6.9Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 12.4% chance of exploitation in 30 days – higher than 96% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 15 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Shiguangwu sgwbox N3	Affected =2.0.25	Fixed in–

AI-suggested

Given the lack of an official patch, European organizations should implement specific mitigations: 1) Restrict network access to the /eshell API endpoint by applying firewall rules or network segmentation to limit exposure only to trusted management networks. 2) Deploy intrusion detection or prevention systems (IDS/IPS) with signatures or heuristics to detect path traversal attempts targeting /eshell. 3) Monitor logs and network traffic for unusual access patterns or attempts to access unauthorized file paths. 4) If possible, disable or restrict the /eshell API functionality until a vendor patch is available. 5) Conduct thorough asset inventories to identify all devices running sgwbox N3 2.0.25 and prioritize their isolation or enhanced monitoring. 6) Engage with the vendor or community to track any forthcoming patches or workarounds. 7) Consider deploying application-layer gateways or reverse proxies that can sanitize or block malicious requests targeting the vulnerable API. 8) Educate security teams about the vulnerability and ensure incident response plans include scenarios involving path traversal exploitation.

Description

A 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.

Impact

For European organizations, this vulnerability poses a risk of unauthorized data disclosure and potential system compromise, especially in environments where Shiguangwu sgwbox N3 devices are deployed in critical network segments. Confidentiality could be compromised by attackers accessing sensitive files, including credentials or configuration data. Integrity and availability impacts are limited but possible if attackers modify or delete critical files after gaining access. The remote, unauthenticated nature of the exploit increases the likelihood of exploitation, particularly in poorly segmented or exposed networks. Organizations in sectors such as telecommunications, industrial control, or enterprise networking that utilize this product could face operational disruptions or data breaches. The absence of vendor patches necessitates reliance on compensating controls, increasing operational overhead. Additionally, the public availability of exploit code lowers the barrier for attackers, including opportunistic threat actors and cybercriminals targeting European infrastructure.

Summary

CVE-2025-14704 identifies a path traversal vulnerability in the Shiguangwu sgwbox N3 device, specifically version 2.0.25. The vulnerability resides in an unspecified function of the /eshell API component, which improperly validates or sanitizes user input, allowing an attacker to manipulate file paths. This manipulation enables traversal outside the intended directory boundaries, potentially exposing sensitive files or system resources. The vulnerability can be exploited remotely without requiring authentication or user interaction, increasing the attack surface significantly. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P) reflects network attack vector, low attack complexity, no privileges or user interaction needed, and partial impact on confidentiality, integrity, and availability. The lack of known active exploits in the wild currently limits immediate widespread impact but does not preclude targeted attacks. The vulnerability could be leveraged to read sensitive configuration files, credentials, or system binaries, potentially leading to further compromise or lateral movement within affected networks.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 22 Dec 2025, 06:07 UTC

Technical details

References

Community reviews

Related threats