Skip to main content

IoT CVE-2025-5748

| EUVDEUVD-2025-17312 HIGH
Exposed Dangerous Method or Function (CWE-749)
2025-06-06 zdi-disclosures@trendmicro.com
8.0
CVSS 3.0 · NVD
View

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Dangerous method exposure prevention
Impact

Risk assessment across multiple signal dimensions: CVSS 8.0 (High) with AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H indicates network-adjacent attack requirement, low attack complexity, requirement for low privileges (but bypassable), no user interaction needed, and high confidentiality, integrity, and availability impact. The CVSS vector reflects a serious vulnerability, though the Adjacent access vector requirement (AV:A) limits exposure compared to network-based attacks. The SSVC framework context: exploitation appears feasible given the exposed method and known ZDI disclosure (ZDI-CAN-26349), automatable attacks are highly probable due to the programmatic nature of OTA uploads, and technical impact is complete system compromise. While specific EPSS scores and KEV inclusion status are not provided in the source data, the combination of ZDI coordination, authentication bypass, and exposed dangerous methods strongly suggests active research and potential POC availability in security communities. Real-world priority is HIGH for any organization operating WOLFBOX EV charger deployments, particularly in fleet/commercial settings where multiple chargers may be affected. The LAN-only requirement reduces exposure in strictly segmented networks but remains critical for most IoT/charger installations with standard network configurations.

Exploit ScenarioDerived

Attack scenario: An attacker on the same network segment (or with network access to the charger's LAN interface) identifies a WOLFBOX Level 2 EV Charger connected to the network. The attacker leverages the known authentication bypass vulnerability to bypass Tuya module authentication requirements. Using the exposed OTA upload method, the attacker crafts a malicious firmware image containing arbitrary code (e.g., reverse shell, credential harvester, or device control logic) and uploads it via the unprotected upload endpoint. The Tuya module accepts and executes the uploaded image without validation. The attacker gains code execution in the Tuya communication module context, and from there can pivot to the host EV charger system, potentially: disabling charging functionality, modifying billing data, extracting user/vehicle credentials, or using the compromised charger as a pivot point for further network attacks. Exploitation is automatable and repeatable, requiring minimal tools (HTTP client, crafted firmware). POC existence is likely given ZDI historical practices, though not explicitly confirmed in provided data.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Mar 14, 2026

Critical remote code execution vulnerability in WOLFBOX Level 2 EV Charger devices that exploits an exposed dangerous method in the Tuya communications module, allowing network-adjacent attackers to upload and execute arbitrary code despite authentication requirements. The authentication bypass mechanism combined with the exposed software upload functionality creates a high-severity attack path that can grant attackers complete control over affected EV charger installations. This vulnerability (formerly ZDI-CAN-26349) presents significant risk to vehicle charging infrastructure and connected IoT deployments relying on Tuya-based communication protocols.

RemediationAI

Immediate remediation steps: (1) Check WOLFBOX and Tuya official security advisories for available firmware patches addressing CVE-2025-5748 and authentication bypass; (2) Apply vendor-provided firmware updates to all affected EV chargers immediately upon availability; (3) Network segmentation: isolate EV charger management interfaces to restricted VLANs with access controls limiting LAN exposure; (4) Disable OTA auto-update if manual update review is feasible; (5) Implement network-level monitoring for suspicious firmware upload attempts to charger devices (watch for firmware update traffic patterns); (6) Reset authentication credentials on affected devices if supported; (7) Monitor Tuya module logs for unauthorized access attempts. Long-term: replace affected devices with patched versions once vendor provides remediation, or migrate to alternative non-Tuya-dependent charger platforms if patches are unavailable. Specific patch versions and vendor advisory links must be obtained from WOLFBOX and Tuya security bulletins.

Affected VersionsENISA

Level 2 EV Charger 3.1.17 (main), 1.2.6 (MCU)

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The vulnerability resides in the Tuya communications module software integrated into WOLFBOX Level 2 EV Chargers. Tuya is a widely-used IoT cloud platform providing connectivity and OTA (Over-The-Air) update capabilities for smart devices. The specific flaw involves CWE-749 (Exposed Dangerous Method or Function), where a method responsible for firmware/software image uploads has been exposed without adequate access controls. The underlying issue is compounded by a secondary authentication bypass vulnerability within the Tuya module's authentication mechanism, allowing attackers to circumvent the intended privilege requirements. This combination—exposed OTA upload functionality plus authentication bypass—creates a direct path to arbitrary code execution on the device's Tuya communication subsystem and potentially the host EV charger system. The LAN-based attack vector indicates the vulnerability is exploitable from devices on the same network segment as the charger.

Know when IoT gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

NVD PRIMARY 8.0 HIGH
AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

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

DescriptionCVE.org

WOLFBOX Level 2 EV Charger LAN OTA Exposed Dangerous Method Remote Code Execution Vulnerability. This vulnerability allows network-adjacent attackers to execute arbitrary code on affected installations of WOLFBOX Level 2 EV Charger. Although authentication is required to exploit this vulnerability, the existing authentication mechanism can be bypassed.

The specific flaw exists within the Tuya communications module software. The issue results from the exposure of a method allowing the upload of crafted software images to the module. An attacker can leverage this vulnerability to execute code in the context of the device. Was ZDI-CAN-26349.

Executive ViewAI

Why It Matters

A critical remote code execution vulnerability in WOLFBOX Level 2 EV Chargers could allow attackers to gain unauthorized control of charging infrastructure despite authentication requirements, potentially disrupting operations and creating liability exposure. Organizations operating these devices should treat this as a priority security incident given the lack of available patches and the device's role in critical energy infrastructure.

Business Impact: High
Compensating Controls

Implement network segmentation isolating EV chargers to dedicated VLAN with restricted access; disable OTA update functionality if operationally feasible; monitor and log all administrative access to charger management interfaces; restrict firmware upload capabilities to specific administrative networks; implement host-based intrusion detection on charger management systems; require VPN for any remote management access; disable Tuya cloud communications if local-only operation is possible; conduct regular security assessments of charger network traffic for anomalies.

Threat Intelligence Overview

EPSS Score
0.2%
Top 62% exploitable
Data Quality
4 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.2%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Controlled
Automatable· derived
No
Human Impact
High

Priority Score

40
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +40
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.

More in IoT

View all
CVE-2025-45988 CRITICAL POC
9.8 Jun 13

A command injection vulnerability (CVSS 9.8). Risk factors: public PoC available.

CVE-2026-29128 CRITICAL POC
10.0 Mar 05

Plaintext daemon credentials in IDC SFX2100 routing config files (zebra, bgpd, ospfd, ripd). CVSS 10.0. PoC available.

CVE-2025-65294 CRITICAL POC
9.8 Dec 10

Remote command execution in Aqara Hub firmware (Camera Hub G3 4.1.9_0027, Hub M2 4.3.6_0027, and Hub M3 4.3.6_0025) stem

CVE-2025-63624 CRITICAL POC
9.8 Feb 03

Kede Electronics IoT smart water meter monitoring platform v1.0 has a SQL injection allowing attackers to compromise the

CVE-2026-101076 CRITICAL POC
9.3 Sep 28

An unauthenticated OS command injection in the CGI handler of Netcore NR289-GE firmware 1.4.5102 lets remote attackers e

CVE-2026-101077 CRITICAL POC
9.3 Sep 28

Unauthenticated network attackers can bypass authentication in the Netcore NR289-GE router's boa_temp web handler and ab

CVE-2026-101075 CRITICAL POC
9.3 Sep 28

Remote unauthenticated OS command injection in Netcore NR289-GE firmware 1.4.5102 allows attackers to execute arbitrary

CVE-2026-101072 CRITICAL POC
9.3 Sep 28

Unauthenticated OS command injection in the Netcore NR289-GE router (firmware 1.4.5102) lets any remote attacker who can

CVE-2026-101039 CRITICAL POC
9.3 Sep 28

A stack-based buffer overflow in the devdiscover service of FAST FAC1900R firmware 20190827_2.0.2 lets unauthenticated r

CVE-2026-25139 CRITICAL POC
9.1 Feb 04

RIOT IoT operating system has an out-of-bounds read vulnerability (CVSS 9.1) that could lead to information disclosure o

CVE-2026-102792 HIGH POC
8.5 Sep 29

Command injection in the Ziroom ZHOME A0101 smart-home hub (firmware 1.0.1.0) allows an attacker with high-privilege aut

CVE-2026-102793 HIGH POC
8.5 Sep 29

Authenticated command injection in Ziroom ZHOME A0101 firmware 1.0.1.0 lets a privileged user execute arbitrary operatin

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy