Quick answers
- Is CVE-2026-40816 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-40816 being exploited in the wild.
- How severe is CVE-2026-40816?
- High severity, with a CVSS score of 7.5, published 27 May 2026.
- Which products and versions are affected?
- MB connect line mbCONNECT24 <= 2.20.0; MB connect line mymbCONNECT24 <= 2.20.0.
- Is there a fix for CVE-2026-40816?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-40816 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-40816?
- Check whether you run MB connect line mbCONNECT24 or MB connect line mymbCONNECT24 at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A SQL injection vulnerability exists in the mb24alarm.php file within the _mb24confi_getTagAlarm function of MB connect line mbCONNECT24 and mymbCONNECT24. The issue stems from improper neutralization of special elements in a SQL SELECT command. An unauthenticated remote attacker can exploit this over the network to execute arbitrary SQL queries. Successful exploitation allows the attacker to read sensitive information from the database, resulting in a total loss of confidentiality. The vulnerability is present in firmware versions up to and including 2.20.0.
Affected products
- MB connect line mbCONNECT24 <= 2.20.0
- MB connect line mymbCONNECT24 <= 2.20.0
Timeline
- 2026-05-27: disclosed
- 2026-05-27: advisory