CVE-2025-5825
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 Firmware Downgrade Remote Code Execution Vulnerability. This vulnerability allows network-adjacent attackers to execute arbitrary code on affected installations of Autel MaxiCharger AC Wallbox Commercial charging stations. 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 firmware update process. The issue results from the lack of proper validation of a firmware image before using it to perform an upgrade. An attacker can leverage this in conjunction with other vulnerabilities to execute arbitrary code in the context of the device. Was ZDI-CAN-26354.
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 confidenceThe vulnerability exists in the firmware update process of Autel MaxiCharger AC Wallbox Commercial charging stations. Attackers with the ability to pair a malicious Bluetooth device can exploit the lack of proper validation of firmware images before performing an upgrade, allowing firmware downgrade and chained exploitation leading to arbitrary code execution in the device context.
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.0/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 charging station hardware label or check the device web interface/admin panel for the model number (e.g., C50, AC Pro, AC Ultra, DC Compact Mobile, DC Compact Pedestal, DC Fast, DC Hipower, DH480)Affected if The model is any of these eight Autel MaxiCharger variants
-
Determine the installed firmware versionAccess the charging station admin interface or use the Autel mobile app to view the firmware version information; typically found under Settings > Device Info or similarAffected if The firmware version is less than 1.39.51 OR less than 1.56.51
-
Check if Bluetooth pairing is enabledAccess the device settings via the web interface or mobile app and verify the Bluetooth pairing configuration statusAffected if Bluetooth pairing is enabled and accessible to unauthorized devices
You are affected if you have an Autel MaxiCharger model with firmware version below 1.39.51 or below 1.56.51 (depending on the version scheme your model uses), and Bluetooth pairing is accessible to potential attackers.
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
Implement cryptographic signature validation for all firmware images prior to upgrade, enforce minimum firmware version checks to prevent downgrade, and restrict Bluetooth pairing through authentication or network segmentation until a vendor patch is applied.
Upgrade to MaxiCharger firmware version 1.39.51 or later (for early firmware branches), or version 1.56.51 or later (for later firmware branches). Contact Autel Energy technical support to confirm the appropriate fixed release for your specific model.
- 1. Identify the specific MaxiCharger model (AC Elite Business C50, AC Pro, AC Ultra, DC Compact Mobile, DC Compact Pedestal, DC Fast, DC Hipower, or DH480) currently deployed
- 2. Determine the current firmware version installed on the device through the device management interface or administrative console
- 3. Download the latest firmware version from Autel's official support website or contact Autel technical support for the firmware file
- 4. Verify the firmware version is 1.39.51 or higher, or 1.56.51 or higher (depending on your model line)
- 5. Follow Autel's official firmware update procedure documented in the device installation manual
- 6. Ensure the Bluetooth pairing process follows security best practices - only pair with trusted devices in secure environments
- 7. After update, verify the firmware version has been successfully applied
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-5825 — 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-5825 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