CVE-2025-48463VulnerabilityPublished 24 Jun 2025Updated 25 Jun 2025

CVE-2025-48463: Advantech Wireless Sensing and Equipment (WISE) · Vulnerability

Affects Advantech Wireless Sensing and Equipment (WISE)Source CVE Database V5

Not known to be exploited · CVSS 3.1 Low.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

3.1Low

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

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

CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N

Attack Vector: Adjacent
Attack Complexity: High
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

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

Attack Vector: Adjacent: The vulnerable component is bound to the network stack, but the attack is limited at the protocol level to a logically adjacent topology. This can mean an attack must be launched from the same shared physical (e.g., Bluetooth or IEEE 802.11) or logical (e.g., local IP subnet) network, or from within a secure or otherwise limited administrative domain (e.g., MPLS, secure VPN to an administrative network zone).
Attack Complexity: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
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 impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 24 Jun 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.

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

AI-suggested

To mitigate this vulnerability, European organizations should take the following specific actions: 1) Immediately assess the deployment of Advantech WISE devices, identifying all instances running the affected version A2.01 B00. 2) Where possible, isolate these devices on segmented networks with strict access controls to limit exposure to potential attackers. 3) Implement network-level encryption such as VPN tunnels or IPsec to secure communications if the device firmware cannot be updated promptly. 4) Monitor network traffic for signs of MitM attacks or unusual session activity targeting these devices. 5) Engage with Advantech support channels to obtain firmware updates or patches as they become available, and plan for timely deployment. 6) Consider deploying additional security controls such as intrusion detection systems (IDS) tailored to detect anomalies in wireless sensor communications. 7) Review and harden access policies around these devices, including restricting administrative access and employing multi-factor authentication where applicable. 8) Conduct regular security audits and penetration testing focusing on wireless sensor networks to identify and remediate similar weaknesses.

Description

Successful exploitation of the vulnerability could allow an attacker to intercept data and conduct session hijacking on the exposed data as the vulnerable product uses unencrypted HTTP communication, potentially leading to unauthorised access or data tampering.

Impact

For European organizations, especially those in industrial sectors such as manufacturing, energy, and critical infrastructure that utilize Advantech WISE devices, this vulnerability poses a significant risk. Intercepted data could reveal sensitive operational parameters or control signals, potentially allowing attackers to disrupt industrial processes or cause physical damage. Session hijacking could enable unauthorized control over equipment, leading to safety hazards or operational downtime. The impact extends to data confidentiality breaches, manipulation of sensor data, and potential cascading failures in automated systems. Given Europe's strong regulatory environment around data protection and critical infrastructure security, exploitation could also lead to compliance violations and reputational damage. Organizations relying on these devices for real-time monitoring and control must consider the risk of operational disruption and data tampering, which could affect supply chains and service continuity.

Summary

CVE-2025-48463 is a vulnerability identified in Advantech's Wireless Sensing and Equipment (WISE) product, specifically affecting version A2.01 B00. The core issue stems from the use of unencrypted HTTP communication channels for data transmission. This lack of encryption exposes the data in transit to interception by attackers who can perform man-in-the-middle (MitM) attacks. Through such interception, an attacker can hijack active sessions, gaining unauthorized access to the system or manipulating the data being transmitted. The vulnerability does not require authentication or user interaction, as it exploits the fundamental communication protocol used by the device. Since the WISE product is typically deployed in industrial and IoT environments for wireless sensing and equipment monitoring, the exposure of sensitive operational data or control commands could lead to significant operational disruptions or data integrity issues. No patches or known exploits in the wild have been reported as of the publication date, but the vulnerability's nature makes it a critical concern for environments relying on secure data transmission. The absence of encryption also suggests that confidentiality, integrity, and availability of data are all at risk if exploited.

CWE-312Cleartext Storage of Sensitive Information (opens in a new tab)
Base weaknessOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The product stores sensitive information in cleartext within a resource that might be accessible to another control sphere.
Implementation · System Configuration · Operation
When storing data in the cloud (e.g., S3 buckets, Azure blobs, Google Cloud Storage, etc.), use the provider's controls to encrypt the data at rest.
Implementation · System Configuration · Operation
In some systems/environments such as cloud, the use of "double encryption" (at both the software and hardware layer) might be required, and the developer might be solely responsible for both layers, instead of shared responsibility with the administrator of the broader system/environment.
OWASP Cheat Sheets
Secure Design Principles (opens in a new tab)
OWASP ASVS 4.0.3
V8.1.6 (opens in a new tab)
V8.2.3 (opens in a new tab)
V8.2.2 (opens in a new tab)
Attack patterns
Retrieve Embedded Sensitive Data (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

csa.gov.sg/alerts-and-advisories/alerts/al-2025-061 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 24 Jun 2025, 02:56 UTC

WeaknessesCWE-312

Technical details

References

Community reviews

Related threats