CVE-2025-5749
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedWOLFBOX 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThis vulnerability in WOLFBOX Level 2 EV Charger devices stems from an uninitialized variable used in handling cryptographic keys for BLE (Bluetooth Low Energy) encrypted communications. An attacker within BLE range can exploit this by leveraging the improperly initialized key variable to bypass authentication entirely and gain unauthorized access to the device.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 3.1.17CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the WOLFBOX charger firmware versionAccess the device admin interface, app, or display menu and locate the firmware/version information section. If you have CLI access, run the appropriate version command. Compare the displayed version number to 3.1.17.Affected if The firmware version is exactly 3.1.17
-
Determine if BLE is enabledCheck the device settings or configuration panel for Bluetooth Low Energy (BLE) connectivity options. Look for a BLE enable/disable toggle or status indicator in the mobile app or device web interface.Affected if BLE is turned ON or set to enabled
-
Verify BLE pairing or authentication is in useInspect the BLE configuration or connection logs to confirm the device uses BLE for encrypted communications, particularly for remote access, app connectivity, or authentication functions.Affected if The device uses BLE for encrypted communication or app-based authentication
-
Review BLE connection logs for anomaliesIf available, examine BLE connection logs or event history for unexpected connection attempts, successful authentications from unknown devices, or authentication bypass events.Affected if There are unexplained BLE connection events or successful authentications without proper credential exchange
A user is affected if their WOLFBOX Level 2 EV Charger runs firmware version 3.1.17 and has BLE enabled for device communication or app connectivity.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataContact WOLFBOX for a firmware update that properly initializes cryptographic key variables before use. Until a patch is available, limit physical proximity to the device and monitor for unauthorized BLE device connections.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-5749 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-5749 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data