CVE-2025-5828
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 wLength Buffer Overflow Remote Code Execution Vulnerability. This vulnerability allows physically present attackers to execute arbitrary code on affected installations of Autel MaxiCharger AC Wallbox Commercial EV chargers. Authentication is not required to exploit this vulnerability. The specific flaw exists within the handling of USB frame packets. The issue results from the lack of proper validation of the length of user-supplied data prior to copying it to a fixed-length buffer. An attacker can leverage this vulnerability to execute code in the context of the device. Was ZDI-CAN-26328.
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 confidenceBuffer overflow in Autel MaxiCharger AC Wallbox Commercial EV chargers when handling USB frame packets. The device fails to validate the length of user-supplied data before copying it to a fixed-length buffer, allowing an attacker with physical access to execute arbitrary code in the device context without 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
- Physical
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:P/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 Autel MaxiCharger modelLocate the device model number on the physical charger unit or in the management interface/web UI. Common models include AC Elite Business C50, AC Pro, AC Ultra, DC Compact Mobile, DC Compact Pedestal, DC Fast, DC Hipower, and DH480.Affected if The model is any of the affected product lines listed in the CVE.
-
Check the current firmware versionAccess the chargers web administration panel, mobile app, or device display menu and navigate to the About/System Info section to find the installed firmware version. Alternatively, query the device API if available.Affected if The firmware version is lower than 1.39.51 or falls between 1.39.51 and 1.56.51 (e.g., 1.40.00 through 1.56.50). Both ranges indicate an unpatched version.
-
Verify USB connectivity is accessibleInspect the device for exposed USB ports or check if USB frame packet handling is enabled in the device configuration settings. On some models, USB may be used for diagnostics, firmware updates, or data export.Affected if USB ports are physically accessible or USB functionality is enabled in the device settings, as this is the attack surface for the buffer overflow.
-
Confirm device is networked or managedDetermine if the device is connected to a management system, fleet controller, or cloud portal that can provide centralized firmware version reporting.Affected if The device is part of a larger charging network; multiple units may be affected simultaneously.
The environment is affected if the device is an Autel MaxiCharger (any model listed) running firmware version lower than 1.39.51 or between 1.39.51 and 1.56.51, and USB ports or USB frame handling are accessible.
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 physical access is required and no authentication needed, immediately apply any vendor firmware updates when available. Until then, restrict physical access to charging stations via secure enclosures or controlled facility access.
Firmware version 1.39.51 or 1.56.51 or later (depending on your current branch)
- 1. Identify the current firmware version of the MaxiCharger device by accessing the device management interface or checking the device settings
- 2. Determine which firmware branch (1.39.x or 1.56.x) your device is running based on the current version
- 3. Download the firmware update from Autel's official support website or contact Autel technical support for the appropriate update file
- 4. Follow the manufacturer's firmware upgrade procedure, which typically involves accessing the device's administrative interface and uploading the firmware file
- 5. After upgrading, verify the new firmware version is 1.39.51 or higher (for 1.39 branch), or 1.56.51 or higher (for 1.56 branch)
- 6. Confirm the vulnerability is remediated by verifying the device operates normally after the update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation4.0 h
- Testing6.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,728.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-5828 — 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-5828 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