Physical authentication bypass via unpersonalized management cards
Published Jun 6, 2025 · Updated Jun 6, 2025
Authentication bypass in WOLFBOX Level 2 EV Charger 3.1.17 (main) and 1.2.6 (MCU) allows physically proximate attackers to gain access. The management-card handler accepts cards that lack per-device personalization, so the same embedded credential is trusted across affected installations. Physical access to the charger is required, and successful use bypasses the card authentication boundary to perform actions reserved for an authorized cardholder.
Summary
What happened
Authentication bypass in WOLFBOX Level 2 EV Charger 3.1.17 (main) and 1.2.6 (MCU) allows physically proximate attackers to gain access. The management-card handler accepts cards that lack per-device personalization, so the same embedded credential is trusted across affected installations. Physical access to the charger is required, and successful use bypasses the card authentication boundary to perform actions reserved for an authorized cardholder.
The record
- CVE
- CVE-2025-5751
- Published
- Jun 6, 2025
- Updated
- Jun 6, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-798, T0859
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 6, 2025CVE publishedPublication date reported by the CVE source.
- Jun 6, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo