# CVE-2025-6678: Autel MaxiCharger AC Wallbox Commercial PIN Missing Authentication Information Disclosure Vulnerability

> Remote attackers can access sensitive credentials without authentication due to missing checks in the Pile API of Autel MaxiCharger units.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Jun 2025
- **Updated:** 25 Jun 2025
- **Also known as:** GHSA-9rgw-7fg2-wjgr

## What is CVE-2025-6678?

CVE-2025-6678 is a high-severity missing authorization vulnerability in Autel MaxiCharger AC Wallbox Commercial, published on 25 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Autel MaxiCharger AC Wallbox Commercial PIN Missing Authentication Information Disclosure Vulnerability. This vulnerability allows remote attackers to disclose sensitive information on affected installations of Autel MaxiCharger AC Wallbox Commercial charging stations. Authentication is not required to exploit this vulnerability.

The specific flaw exists within the Pile API. The issue results from the lack of authentication prior to allowing access to functionality. An attacker can leverage this vulnerability to disclose credentials, leading to further compromise. Was ZDI-CAN-26352.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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

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-6678?

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

## Is CVE-2025-6678 being exploited?

There is no known exploitation of CVE-2025-6678 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-6678 and fix it if it is affected.

What it is: CVE-2025-6678 is a high-severity missing authorization vulnerability in Autel MaxiCharger AC Wallbox Commercial, published on 25 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-6678 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-6678/ (Markdown: https://insights.sbomify.com/CVE-2025-6678/index.md)
```

## Sources

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

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