VulnerabilityPublished 6 Jun 2025

CVE-2025-5749: WOLFBOX Level 2 EV Charger · Use of Uninitialized Variable

Affects WOLFBOX Level 2 EV ChargerSource CVE Database V5

Not known to be exploited · CVSS 6.3 Medium.

Data as of 26 Oct 2026, 12:55 UTC

CVSS 3.0 base score

6.3Medium

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

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

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

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

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: 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: 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 on the impacted component.
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 impacted component 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 impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 6 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 26 Oct 2026.

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 or the CVSS exploit maturity 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 using WOLFBOX Level 2 EV Chargers should prioritize the following actions: 1) Apply firmware updates as soon as they become available from WOLFBOX, even though no patches are currently listed, maintain close communication with the vendor for timely releases. 2) Implement network segmentation to isolate EV chargers from critical IT and OT networks, limiting the potential for lateral movement if a charger is compromised. 3) Employ network-level access controls such as firewalls and BLE signal filtering to restrict access to authorized devices only. 4) Monitor network traffic for anomalous BLE communication patterns that could indicate exploitation attempts. 5) Conduct regular security assessments and penetration testing on EV charging infrastructure to identify and remediate weaknesses proactively. 6) Engage with vendors to ensure secure key management practices and request transparency on cryptographic implementations. 7) Consider deploying additional authentication layers or VPN tunnels for remote management interfaces to compensate for the authentication bypass risk.

Description

WOLFBOX Level 2 EV Charger BLE Encryption Keys Uninitialized Variable Authentication Bypass Vulnerability. This vulnerability allows network-adjacent attackers to bypass authentication on affected installations of WOLFBOX Level 2 EV Charger devices. Authentication is not required to exploit this vulnerability. The specific flaw exists within the handling of cryptographic keys used in vendor-specific encrypted communications. The issue results from the lack of proper initialization of a variable prior to accessing it. An attacker can leverage this vulnerability to bypass authentication on the system. Was ZDI-CAN-26295.

Impact

For European organizations, the impact of this vulnerability could be significant given the increasing adoption of EV infrastructure across the continent. Unauthorized access to EV chargers could lead to disruptions in charging availability, affecting fleet operations, public charging stations, and private installations. This could result in operational downtime, financial losses, and reputational damage, especially for service providers and municipalities relying on these chargers. Furthermore, compromised chargers could be leveraged as entry points into corporate or municipal networks, potentially exposing sensitive data or enabling lateral movement. The confidentiality impact is limited but not negligible, as attackers might intercept or manipulate encrypted communications. Integrity and availability impacts are more pronounced, with the possibility of unauthorized control or denial of service. Given the strategic push for green energy and EV adoption in Europe, ensuring the security of charging infrastructure is critical to maintaining trust and operational continuity.

CWE-457Use of Uninitialized Variable (opens in a new tab)
Variant weaknessLikelihood of exploit: High
The code uses a variable that has not been initialized, leading to unpredictable or unintended results.
Implementation · Attack Surface Reduction
Ensure that critical variables are initialized before first use.
Build and Compilation · Compilation or Build Hardening
Most compilers will complain about the use of uninitialized variables if warnings are turned on.
Implementation · Operation
When using a language that does not require explicit declaration of variables, run or compile the software in a mode that reports undeclared or unknown variables. This may indicate the presence of a typographic error in the variable's name.
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

zerodayinitiative.com/advisories/ZDI-25-328/ (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 8 Jul 2025, 03:58 UTC

WeaknessesCWE-457

Technical details

References

Community reviews

Related threats