CVE-2025-5824
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 · uneditedAutel MaxiCharger AC Wallbox Commercial Origin Validation Error Authentication Bypass Vulnerability. This vulnerability allows network-adjacent attackers to bypass authentication on affected installations of Autel MaxiCharger AC Wallbox Commercial. An attacker must first obtain the ability to pair a malicious Bluetooth device with the target system in order to exploit this vulnerability. The specific flaw exists within the handling of bluetooth pairing requests. The issue results from insufficient validation of the origin of commands. An attacker can leverage this vulnerability to bypass authentication on the system. Was ZDI-CAN-26353.
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 · high confidenceThis is a Bluetooth authentication bypass vulnerability in Autel MaxiCharger AC Wallbox Commercial EV chargers. Attackers with the ability to pair a malicious Bluetooth device can exploit insufficient origin validation in the bluetooth pairing request handling to bypass system authentication.
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< 1.39.51< 1.56.51< 1.39.51< 1.56.51< 1.39.51< 1.56.51< 1.39.51< 1.56.51< 1.39.51< 1.56.51< 1.39.51< 1.56.51< 1.39.51< 1.56.51< 1.39.51< 1.56.51CVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:H/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 Autel MaxiCharger modelLocate the physical charger or consult asset inventory to confirm the exact model (e.g., MaxiCharger AC Elite Business C50, AC Pro, AC Ultra, DC Compact Mobile, DC Compact Pedestal, DC Fast, DC Hipower, or DH480)Affected if The model is any of the affected products listed in the CVE
-
Determine the installed firmware versionAccess the charger management interface (local display, admin web portal, or mobile app) and navigate to the firmware or system information section to retrieve the current firmware version numberAffected if The firmware version is less than 1.39.51 or less than 1.56.51 (note: some models may follow either version branch)
-
Check if Bluetooth pairing is enabledAccess the charger settings via the admin interface or mobile app and verify whether Bluetooth pairing functionality is turned on or accessibleAffected if Bluetooth pairing is enabled and discoverable, allowing potential attackers to initiate pairing requests
-
Verify Bluetooth accessibilityUse a Bluetooth scanner or compatible device to detect whether the charger is discoverable and accepting pairing connections from nearby devicesAffected if The charger is discoverable and accepts pairing requests from unauthorized devices
You are affected if your Autel MaxiCharger is running firmware version below 1.39.51 or below 1.56.51 AND has Bluetooth pairing enabled or accessible to unauthorized devices.
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.
dbcve · scoped1.39.511.56.51
Since the vulnerability is in vendor firmware, organizations should implement compensating controls including restricting Bluetooth pairing to authorized devices only, network segmentation of charging infrastructure, and monitoring for unauthorized Bluetooth device associations until vendor firmware updates are available.
Firmware version 1.39.51 or higher, or version 1.56.51 or higher (depending on device series)
- Identify the current firmware version of the affected MaxiCharger device by accessing the device management interface or checking system information
- Determine which firmware branch is applicable to your device (1.x or 2.x series) based on your current version
- Download the appropriate firmware update from Autel's official support portal or contact Autel technical support
- Follow the manufacturer's documented firmware update procedure, typically involving uploading the firmware file through the device's administrative web interface or mobile app
- Verify the firmware upgrade was successful by confirming the new version number in the device settings
- After upgrade, ensure Bluetooth pairing is disabled if not needed, or review and re-authorize only trusted Bluetooth devices
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-5824 — 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-5824 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