Autel MaxiCharger Single up to 1.03.51 Management Endpoints improper authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 10.0 | $0-$5k | 0.00 |
Summary
A vulnerability classified as very critical has been found in Autel MaxiCharger Single up to 1.03.51. This impacts an unknown function of the component Management Endpoints. Performing a manipulation results in improper authorization. This vulnerability was named CVE-2026-8983. The attack may be initiated remotely. There is no available exploit.
Details
A vulnerability was found in Autel MaxiCharger Single up to 1.03.51. It has been classified as very critical. This affects some unknown processing of the component Management Endpoints. The manipulation with an unknown input leads to a improper authorization vulnerability. CWE is classifying the issue as CWE-285. The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
Autel Maxi Charger Single firmware through V1.03.51 contains a hard-coded authentication token that bypasses authorization checks for multiple management endpoints. An attacker can supply the special token value to invoke privileged functionality without valid authentication.
The advisory is shared at cyberdanube.com. This vulnerability is uniquely identified as CVE-2026-8983 since 05/19/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 07/21/2026). MITRE ATT&CK project uses the attack technique T1548.002 for this issue.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
- 1.03.0
- 1.03.1
- 1.03.2
- 1.03.3
- 1.03.4
- 1.03.5
- 1.03.6
- 1.03.7
- 1.03.8
- 1.03.9
- 1.03.10
- 1.03.11
- 1.03.12
- 1.03.13
- 1.03.14
- 1.03.15
- 1.03.16
- 1.03.17
- 1.03.18
- 1.03.19
- 1.03.20
- 1.03.21
- 1.03.22
- 1.03.23
- 1.03.24
- 1.03.25
- 1.03.26
- 1.03.27
- 1.03.28
- 1.03.29
- 1.03.30
- 1.03.31
- 1.03.32
- 1.03.33
- 1.03.34
- 1.03.35
- 1.03.36
- 1.03.37
- 1.03.38
- 1.03.39
- 1.03.40
- 1.03.41
- 1.03.42
- 1.03.43
- 1.03.44
- 1.03.45
- 1.03.46
- 1.03.47
- 1.03.48
- 1.03.49
- 1.03.50
- 1.03.51
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 10.0VulDB Meta Temp Score: 10.0
VulDB Base Score: 10.0
VulDB Temp Score: 10.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Improper authorizationCWE: CWE-285 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
05/19/2026 CVE reserved07/21/2026 Advisory disclosed
07/21/2026 VulDB entry created
07/21/2026 VulDB entry last update
Sources
Advisory: cyberdanube.comStatus: Not defined
CVE: CVE-2026-8983 (🔒)
GCVE (CVE): GCVE-0-2026-8983
GCVE (VulDB): GCVE-100-381093
Entry
Created: 07/21/2026 23:42Changes: 07/21/2026 23:42 (52)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.