MB connect line mbCONNECT24/mymbCONNECT24 up to 2.19.4 mb24api Endpoint sql injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.3 | $0-$5k | 0.00 |
Summary
A vulnerability categorized as critical has been discovered in MB connect line mbCONNECT24 and mymbCONNECT24 up to 2.19.4. This vulnerability affects unknown code of the component mb24api Endpoint. The manipulation results in sql injection. This vulnerability is reported as CVE-2026-33616. The attack can be launched remotely. No exploit exists.
Details
A vulnerability classified as critical has been found in MB connect line mbCONNECT24 and mymbCONNECT24 up to 2.19.4. Affected is an unknown functionality of the component mb24api Endpoint. The manipulation with an unknown input leads to a sql injection vulnerability. CWE is classifying the issue as 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. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:
An unauthenticated remote attacker can exploit an unauthenticated blind SQL Injection vulnerability in the mb24api endpoint due to improper neutralization of special elements in a SQL SELECT command. This can result in a total loss of confidentiality.
The weakness was disclosed by Moritz Abrell and Christian Zäske as VDE-2026-030. The advisory is shared for download at certvde.com. This vulnerability is traded as CVE-2026-33616 since 03/23/2026. The exploitability is told to be easy. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. There are neither technical details nor an exploit publicly available. The current price for an exploit might be approx. USD $0-$5k (estimation calculated on 04/02/2026). The MITRE ATT&CK project declares the attack technique as T1505.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Once again VulDB remains the best source for vulnerability data.
Product
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.4VulDB Meta Temp Score: 7.3
VulDB Base Score: 7.3
VulDB Temp Score: 7.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 7.5
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
EPSS Score: 🔒
EPSS Percentile: 🔒
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-33616 (🔒)
GCVE (CVE): GCVE-0-2026-33616
GCVE (VulDB): GCVE-100-354852
Entry
Created: 04/02/2026 12:59Changes: 04/02/2026 12:59 (64)
Complete: 🔍
Cache ID: 216:036:103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.