CVE-2025-6678
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 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.
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 confidenceThis vulnerability in Autel MaxiCharger AC Wallbox Commercial charging stations allows remote unauthenticated attackers to access the Pile API and disclose sensitive credentials. The flaw stems from missing authentication checks on specific API endpoints, enabling attackers to obtain credentials that can be used for further compromise of the charging station system.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/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.
-
Check the charging station firmware versionAccess the station admin interface or API and retrieve the firmware version information. This is typically found in the device status or system settings page.Affected if The installed firmware version is below 1.39.51, or falls between 1.39.51 and 1.56.51 inclusive. Firmware versions 1.39.51 and 1.56.51 and above are not affected.
-
Verify network exposure of the Pile APIFrom a network perspective, attempt to reach the Pile API endpoints (typically on port 80/443 or the station's web service port) from an unauthenticated network perspective. Check if the device management interface is exposed to untrusted networks.Affected if The charging station management interface or Pile API endpoints are accessible from an untrusted network without any authentication required.
-
Test for missing authentication on API endpointsSend an HTTP GET request to common Pile API endpoints without providing any authentication headers or credentials. Observe if the request returns sensitive data such as credentials or system information.Affected if The API responds with sensitive information or credentials without requiring any authentication token or credentials in the request.
-
Review access logs for unauthenticated API accessIf available, examine the station's access logs or management system logs for any API calls that were made without authentication tokens, particularly those accessing credential-related endpoints.Affected if Logs show API requests to sensitive endpoints that lack authentication tokens or originated from unauthenticated sources.
You are affected if your Autel MaxiCharger device runs firmware version below 1.39.51 or between 1.39.51-1.56.51 AND the Pile API endpoints are network-accessible without authentication.
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.
From vendor data1.39.511.56.51
Implement authentication requirements on all Pile API endpoints to prevent unauthorized access to sensitive information. Restrict network exposure of the charging station management interface and monitor for unauthorized access attempts.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-6678 — 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-6678 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