United Chargers Grizzl-E Smart OCPP Backend hard-coded credentials
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 10.0 | $0-$5k | 0.00+ |
Summary
A vulnerability was found in United Chargers Grizzl-E Smart and classified as very critical. The affected element is an unknown function of the component OCPP Backend. Executing a manipulation can lead to hard-coded credentials. This vulnerability is handled as CVE-2026-131811. The attack can be executed remotely. There is not any exploit available.
Details
A vulnerability classified as very critical was found in United Chargers Grizzl-E Smart (the affected version is unknown). This vulnerability affects an unknown code of the component OCPP Backend. The manipulation with an unknown input leads to a hard-coded credentials vulnerability. The CWE definition for the vulnerability is CWE-798. The product contains hard-coded credentials, such as a password or cryptographic key. As an impact it is known to affect confidentiality, integrity, and availability.
This vulnerability was named CVE-2026-131811. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. The technical details are unknown and an exploit is not available. The structure of the vulnerability defines a possible price range of USD $0-$5k at the moment (estimation calculated on 11/18/2026). This vulnerability is assigned to T1110.001 by the MITRE ATT&CK project.
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 best quality of vulnerability data, you may have to visit VulDB.
Product
Vendor
Name
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: Hard-coded credentialsCWE: CWE-798 / CWE-259 / CWE-255
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
11/18/2026 Advisory disclosed11/18/2026 VulDB entry created
11/18/2026 VulDB entry last update
Sources
Status: Not definedCVE: CVE-2026-131811 (🔒)
GCVE (CVE): GCVE-0-2026-131811
GCVE (VulDB): GCVE-100-439786
Entry
Created: 11/18/2026 21:45Changes: 11/18/2026 21:45 (47)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.