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

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

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

Not known to be exploited · CVSS 8.1 High.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

8.1High

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

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

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

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

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: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
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: None: There is no loss of confidentiality within the impacted component.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

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

AI-suggested

1. Network Segmentation: Immediately isolate Advantech WISE devices from public and less trusted networks. Implement strict network segmentation to limit access to these devices only to authorized management systems. 2. Access Control: Deploy firewall rules and access control lists (ACLs) to block unauthorized Modbus TCP traffic from untrusted sources. Only allow Modbus TCP communication from known, secure management stations. 3. Monitoring and Logging: Enable detailed logging of Modbus TCP traffic and monitor for anomalous commands or unexpected relay activations. Use intrusion detection systems (IDS) tailored for industrial protocols to detect potential exploitation attempts. 4. Device Hardening: Review device configurations to disable any unnecessary services or interfaces that could be exploited. If possible, change default network settings to reduce exposure. 5. Vendor Coordination: Engage with Advantech for updates on patches or firmware fixes addressing this vulnerability. Plan for timely deployment of security updates once available. 6. Incident Response Preparedness: Develop and test response procedures for potential exploitation scenarios, including rapid isolation of affected devices and recovery of control systems. 7. Physical Safeguards: Where feasible, implement physical controls or manual overrides for critical relay channels to mitigate risks from remote manipulation. 8. Network Access Controls: Employ VPNs or secure tunnels with strong authentication for remote access to OT devices to prevent unauthorized Modbus TCP traffic.

Description

Successful exploitation of the vulnerability could allow an unauthenticated, remote attacker to send Modbus TCP packets to manipulate Digital Outputs, potentially allowing remote control of relay channel which may lead to operational or safety risks.

Impact

For European organizations, particularly those in industrial sectors such as manufacturing, energy, utilities, and critical infrastructure, this vulnerability poses a significant risk. The ability to remotely manipulate relay channels could disrupt automated processes, leading to production downtime, equipment damage, or safety incidents that endanger personnel. Given the widespread use of Modbus TCP in industrial environments, exploitation could compromise the integrity and availability of operational technology (OT) systems. This may result in financial losses, regulatory penalties, and reputational damage. Additionally, safety risks arising from unintended control of physical devices could have severe consequences, including injury or environmental harm. The vulnerability's unauthenticated nature means that attackers do not need valid credentials, increasing the likelihood of exploitation if network access controls are insufficient. European organizations with network-exposed Advantech WISE devices or inadequate segmentation between IT and OT networks are particularly vulnerable. The threat also aligns with increasing concerns about cyberattacks targeting European critical infrastructure, where disruption of industrial control systems is a strategic objective for some threat actors.

CWE-863Incorrect Authorization (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #17OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.
Architecture and Design
Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries.
Architecture and Design
Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.8 (opens in a new tab)
V13.4.2 (opens in a new tab)
V7.2.2 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

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

WeaknessesCWE-863

Technical details

References

Community reviews

Related threats