CVE-2025-5822
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 Technician API Incorrect Authorization Privilege Escalation Vulnerability. This vulnerability allows remote attackers to escalate privileges on affected installations of Autel MaxiCharger AC Wallbox Commercial charging stations. An attacker must first obtain a low-privileged authorization token in order to exploit this vulnerability. The specific flaw exists within the implementation of the Autel Technician API. The issue results from incorrect authorization. An attacker can leverage this vulnerability to escalate privileges to resources normally protected from the user. Was ZDI-CAN-26325.
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 Autel MaxiCharger AC Wallbox Commercial charging station contains an incorrect authorization vulnerability in its Technician API. Attackers with a low-privileged authorization token can escalate privileges to access resources that should be restricted to higher-privilege users. This allows unauthorized access to administrative or technician-level functions that should be protected.
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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 charging station model and firmware versionAccess the device management interface or use the device's web UI, API, or diagnostic port to retrieve the model name and installed firmware version. This is typically found in the device status page, system information section, or via an API endpoint like /api/device/info.Affected if The firmware version is below 1.39.51 or below 1.56.51 (the specific threshold depends on hardware variant). Compare your installed version against these affected ranges.
-
Locate the Technician API endpointReview the device's API documentation or enumerate available API endpoints on the device (commonly at /api/technician/* or similar paths). Determine if the Technician API is exposed and accessible on the network.Affected if The Technician API endpoint is exposed and reachable from the network where low-privileged users can access it.
-
Verify authorization configuration for Technician APIInspect the device's role-based access control (RBAC) or authorization settings for the Technician API. Check if low-privilege tokens can invoke Technician-level API calls without proper privilege escalation checks.Affected if Low-privilege authorization tokens can successfully call Technician API functions that should require higher privileges.
-
Review user accounts and assigned privilege levelsList all configured user accounts on the device and their assigned roles/privilege levels. Identify any accounts with low-privilege roles that may be able to access technician-level functions.Affected if There exist low-privilege accounts that can access functions restricted to administrator or technician roles.
You are affected if your Autel MaxiCharger device runs firmware version below 1.39.51 or below 1.56.51 AND the Technician API is accessible with low-privilege authorization tokens that can escalate to administrative functions.
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
Apply the vendor-supplied firmware patch when available. Until then, restrict network access to the charging station's management interface and monitor for unauthorized privilege escalation attempts.
Firmware 1.39.51 or 1.56.51 (or later) - contact Autel Energy for exact per-model release
- 1. Identify the current firmware version of the affected MaxiCharger device via the device admin interface or API
- 2. Determine the appropriate firmware branch (1.39.x or 1.56.x) for your device model
- 3. Obtain the firmware update from Autel Energy official support channels or through your authorized Autel dealer
- 4. Schedule maintenance window as the update may require brief downtime
- 5. Apply firmware update following Autel's documented upgrade procedure for your specific device model
- 6. After update, verify the device is operational and confirm the new firmware version displays 1.39.51 or higher, or 1.56.51 or higher depending on branch
- 7. Test that the Technician API authorization controls function correctly post-update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-5822 — 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-5822 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