CVE-2025-5823
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 Serial Number Exposed Dangerous Method Information Disclosure Vulnerability. This vulnerability allows remote attackers to disclose sensitive information on affected installations of Autel MaxiCharger AC Wallbox Commercial EV chargers. Authentication is required to exploit this vulnerability. The specific flaw exists within the implementation of the Autel Technician API. The issue results from an exposed dangerous method. An attacker can leverage this vulnerability to disclose credentials, leading to further compromise. Was ZDI-CAN-26351.
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 is an information disclosure vulnerability in the Autel MaxiCharger AC Wallbox Commercial EV chargers. The Autel Technician API contains an exposed dangerous method that allows authenticated remote attackers to disclose sensitive information, specifically credentials. The vulnerability requires authentication to exploit but can lead to further system compromise.
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
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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 charger modelLocate the device label on the charger unit or access the charger web interface to view the model information (e.g., MaxiCharger AC Elite Business C50, AC Pro, AC Ultra, DC Compact, DC Fast, DC Hipower, or DH480)Affected if The model is one of the affected products listed in the CVE (C50, AC Pro, AC Ultra, DC Compact Mobile, DC Compact Pedestal, DC Fast, DC Hipower, or DH480)
-
Check the installed firmware versionAccess the charger administrative web interface and navigate to System Settings or Device Information to view the firmware version. Alternatively, query the device API for firmware version informationAffected if The firmware version is below 1.39.51 or below 1.56.51 (both thresholds indicate vulnerability)
A user is affected if their Autel MaxiCharger is one of the affected models and is running firmware versions below 1.39.51 or 1.56.51 with the Autel Technician API accessible to network 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
Restrict access to the Autel Technician API and implement proper authentication and authorization controls. Contact Autel for available patches and ensure the device firmware is updated once available. Network segmentation can also limit exposure.
Firmware version 1.39.51 or 1.56.51 (or latest stable release)
- Verify current firmware version on the affected Autel MaxiCharger device through the admin interface or device settings
- Contact Autel Energy technical support to obtain the firmware update to version 1.39.51 or 1.56.51 (or latest stable release)
- Review Autel Energy's official security advisory or release notes for the firmware update
- Download the firmware update from Autel Energy's official support portal or obtain directly from vendor
- Apply the firmware update following Autel's standard update procedure, typically via the device's web interface or dedicated management software
- After update, verify the Autel Technician API no longer exposes dangerous methods and credentials cannot be disclosed
- Confirm the new firmware version is 1.39.51 or higher, or 1.56.51 or higher
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-5823 — 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-5823 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