# CVE-2025-5824: Autel MaxiCharger AC Wallbox Commercial Origin Validation Error Authentication Bypass Vulnerability

> Network-adjacent attackers can bypass authentication on Autel MaxiCharger AC Wallbox Commercial by pairing a malicious Bluetooth device due to insufficient origin validation.

- **Severity:** Medium 5.0 (`CVSS:3.0/AV:A/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Jun 2025
- **Updated:** 25 Jun 2025
- **Also known as:** GHSA-vjqh-vxpx-8294

## What is CVE-2025-5824?

CVE-2025-5824 is a medium-severity authentication bypass vulnerability in Autel MaxiCharger AC Wallbox Commercial, published on 25 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Autel 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.

Weakness: CWE-346 (Origin Validation Error)

## Which versions are affected by CVE-2025-5824?

It affects 9 products.


Products: Autel Maxicharger Ac Elite Business C50 Firmware, Autel Maxicharger Ac Pro Firmware, Autel Maxicharger Ac Ultra Firmware, Autel Maxicharger Dc Compact Mobile Firmware, Autel Maxicharger Dc Compact Pedestal Firmware, Autel Maxicharger Dc Fast Firmware, Autel Maxicharger Dc Hipower Firmware, Autel Maxicharger Dh480 Firmware, Autel Maxicharger Single Charger Firmware.

## How do I fix CVE-2025-5824?

No fix has been published for CVE-2025-5824 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-5824 being exploited?

There is no known exploitation of CVE-2025-5824 in the wild and no public exploit code.

## Other vulnerabilities in Autel MaxiCharger AC Wallbox Commercial

- [CVE-2025-5827](https://insights.sbomify.com/CVE-2025-5827/): Memory corruption in Autel MaxiCharger AC Wallbox Commercial (high 8.8)
- [CVE-2025-5830](https://insights.sbomify.com/CVE-2025-5830/): Memory corruption in Autel MaxiCharger AC Wallbox Commercial (high 8.8)
- [CVE-2024-23957](https://insights.sbomify.com/CVE-2024-23957/): Memory corruption in MaxiCharger AC Elite Business C50 (high 8.8)
- [CVE-2024-7795](https://insights.sbomify.com/CVE-2024-7795/): Memory corruption in MaxiCharger AC Elite Business C50 (high 8.8)
- [CVE-2024-23959](https://insights.sbomify.com/CVE-2024-23959/): Memory corruption in MaxiCharger AC Elite Business C50 (high 8.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-5824 and fix it if it is affected.

What it is: CVE-2025-5824 is a medium-severity authentication bypass vulnerability in Autel MaxiCharger AC Wallbox Commercial, published on 25 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-5824 in the wild and no public exploit code.

Affected product: Autel MaxiCharger AC Wallbox Commercial. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-5824/ (Markdown: https://insights.sbomify.com/CVE-2025-5824/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-5824
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-5824
- OSV: https://osv.dev/vulnerability/CVE-2025-5824

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-5824/
Summaries are generated and may contain mistakes; the official description above is the record.