VulnerabilityPublished 6 Jun 2025

CVE-2025-5751: WOLFBOX Level 2 EV Charger · Use of Hard-coded Credentials

Affects WOLFBOX Level 2 EV ChargerSource CVE Database V5

Not known to be exploited · CVSS 4.6 Medium.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.0 base score

4.6Medium

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

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

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

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

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

Attack Vector: Physical: The attack requires the attacker to physically touch or manipulate the vulnerable component. Physical interaction may be brief or persistent.
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: None: There is no impact to availability within 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

Mitigation should focus on both immediate and long-term measures. Immediately, organizations should enforce strict physical security controls around EV charging stations to prevent unauthorized physical access. This includes surveillance, access restrictions, and tamper-evident seals on management card interfaces. Network segmentation is critical; chargers should be isolated from sensitive networks to limit lateral movement if compromised. Monitoring and logging of charger management activities should be implemented to detect anomalous behavior. In the longer term, WOLFBOX should be urged to release firmware updates that eliminate hard-coded credentials by implementing unique, personalized management cards or alternative strong authentication mechanisms. Organizations should plan for timely deployment of such patches once available. Additionally, conducting regular security assessments of EV infrastructure and incorporating security requirements into procurement processes can reduce exposure to similar vulnerabilities.

Description

WOLFBOX Level 2 EV Charger Management Card Hard-coded Credentials Authentication Bypass Vulnerability. This vulnerability allows physically present attackers to bypass authentication on affected installations of WOLFBOX Level 2 EV Charger. Authentication is not required to exploit this vulnerability. The specific flaw exists within the handling of management cards. The issue results from the lack of personalization of management cards. An attacker can leverage this vulnerability to bypass authentication on the system. Was ZDI-CAN-26292.

Impact

For European organizations, especially those involved in EV infrastructure, this vulnerability poses a tangible risk. Unauthorized physical access to charging stations could lead to manipulation of charging operations, potentially causing service disruptions or damage to EV batteries and hardware. This could undermine trust in EV infrastructure reliability and safety, impacting public and private charging networks. Critical infrastructure operators, fleet managers, and public charging station providers may face operational disruptions and reputational damage. Furthermore, attackers could leverage compromised chargers as entry points for broader network attacks if the chargers are connected to corporate or utility networks. The lack of authentication requirement lowers the barrier for exploitation, increasing risk in environments where physical security is not tightly controlled. Given the increasing adoption of EVs across Europe, the vulnerability could affect a wide range of stakeholders from municipal operators to private enterprises.

CWE-798Use of Hard-coded Credentials (opens in a new tab)
Base weaknessLikelihood of exploit: HighOWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
The product contains hard-coded credentials, such as a password or cryptographic key.
Architecture and Design
For outbound authentication: store passwords, keys, and other credentials outside of the code in a strongly-protected, encrypted configuration file or database that is protected from access by all outsiders, including other local users on the same system. Properly protect the key (CWE-320).
Architecture and Design
For inbound authentication: Rather than hard-code a default username and password, key, or other authentication credentials for first time logins, utilize a "first login" mode that requires the user to enter a unique strong password or key.
Architecture and Design
If the product must contain hard-coded credentials or they cannot be removed, perform access control checks and limit which entities can access the feature that requires the hard-coded credentials. For example, a feature might only be enabled through the system console instead of through a network connection.
OWASP Cheat Sheets
Key Management (opens in a new tab)
REST Security (opens in a new tab)
JSON Web Token for Java (opens in a new tab)
OWASP Authentication (opens in a new tab)
OWASP ASVS 4.0.3
V2.10.4 (opens in a new tab)
V6.4.1 (opens in a new tab)
V3.5.2 (opens in a new tab)
Attack patterns
Read Sensitive Constants Within an Executable (opens in a new tab)
Try Common or Default Usernames and Passwords (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

zerodayinitiative.com/advisories/ZDI-25-330/ (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-798

Technical details

References

Community reviews

Related threats