MB connect line mbCONNECT24/mymbCONNECT24 up to 2.19.4 Setinfo Endpoint sql injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.1 | $0-$5k | 2.07 |
Summary
A vulnerability was found in MB connect line mbCONNECT24 and mymbCONNECT24 up to 2.19.4. It has been rated as critical. This affects an unknown part of the component Setinfo Endpoint. The manipulation leads to sql injection. This vulnerability is documented as CVE-2026-33615. The attack can be initiated remotely. There is not any exploit available.
Details
A vulnerability was found in MB connect line mbCONNECT24 and mymbCONNECT24 up to 2.19.4. It has been rated as critical. This issue affects an unknown function of the component Setinfo Endpoint. The manipulation with an unknown input leads to a sql injection vulnerability. Using CWE to declare the problem leads to CWE-89. The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
An unauthenticated remote attacker can exploit an unauthenticated SQL Injection vulnerability in the setinfo endpoint due to improper neutralization of special elements in a SQL UPDATE command. This can result in a total loss of integrity and availability.
The weakness was released by Moritz Abrell and Christian Zäske as VDE-2026-030. It is possible to read the advisory at certvde.com. The identification of this vulnerability is CVE-2026-33615 since 03/23/2026. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 04/02/2026). The attack technique deployed by this issue is T1505 according to MITRE ATT&CK.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.2VulDB Meta Temp Score: 8.1
VulDB Base Score: 7.3
VulDB Temp Score: 7.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 9.1
CNA Vector (CERTVDE): 🔒
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: Sql injectionCWE: CWE-89 / CWE-74 / CWE-707
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
03/23/2026 CVE reserved04/02/2026 Advisory disclosed
04/02/2026 VulDB entry created
04/02/2026 VulDB entry last update
Sources
Advisory: VDE-2026-030Researcher: Moritz Abrell, Christian Zäske
Status: Not defined
CVE: CVE-2026-33615 (🔒)
GCVE (CVE): GCVE-0-2026-33615
GCVE (VulDB): GCVE-100-354851
Entry
Created: 04/02/2026 12:59Changes: 04/02/2026 12:59 (64)
Complete: 🔍
Cache ID: 216:17B:103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.