CVE-2025-62630: Advantech DeviceOn/iEdge · Path Traversal
Affects Advantech DeviceOn/iEdgeSource CVE Database V5
Not known to be exploited · CVSS 8.8 High.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.7% chance of exploitation in 30 days – higher than 53% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 6 Nov 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-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Advantech DeviceOn/iEdge | Affected
| Fixed in– |
AI-suggested
1. Monitor Advantech communications closely and apply official patches immediately upon release. 2. Until patches are available, restrict file upload capabilities to trusted users and isolate DeviceOn/iEdge systems within segmented network zones with strict access controls. 3. Implement robust input validation and sanitization at network boundaries or proxy layers to detect and block directory traversal patterns in file uploads. 4. Employ application-layer firewalls or intrusion detection/prevention systems (IDS/IPS) configured to identify suspicious file upload behaviors. 5. Conduct regular audits of device configurations and file system integrity to detect unauthorized changes. 6. Limit privileges of accounts interacting with DeviceOn/iEdge to the minimum necessary and enforce strong authentication mechanisms. 7. Educate operational technology (OT) and IT teams about this vulnerability and establish incident response plans tailored to industrial environments. 8. Consider deploying endpoint detection and response (EDR) solutions capable of identifying anomalous process executions on affected devices.
Description
Due to insufficient sanitization, an attacker can upload a specially crafted configuration file to traverse directories and achieve remote code execution with system-level permissions.