Skip to main content
VulnerabilityPublished

CVE-2026-40823: MB connect line mbCONNECT24 · SQL Injection

Affects MB connect line mbCONNECT24Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.0 High.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 4.0 base score
7.0High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 15% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
MB connect linembCONNECT24Affected
  • <=2.20.0
Fixed in–
MB connect linemymbCONNECT24Affected
  • <=2.20.0
Fixed in–
MB connect linembCONNECT24Affected
  • =2.20.0
Fixed in–
MB connect linemymbCONNECT24Affected
  • =2.20.0
Fixed in–
HelmholzmyREX24V2Affected
  • <=2.20.0
Fixed in–
HelmholzmyREX24V2.virtualAffected
  • <=2.20.0
Fixed in–

AI-suggested

Since the product is not a cloud service, remediation depends on vendor updates or workarounds. Organizations should monitor the vendor advisory for updates and apply any official fixes once released. Until then, restrict access to the affected function to trusted users and consider additional network-level protections to limit exposure.

Description

A high privileged remote attacker can exploit an unauthenticated SQL Injection vulnerability in the DevSerialReset function due to improper neutralization of special elements in a SQL UPDATE command allowing for reading the whole database and changing values in a non critical table. This can result in a total loss of confidentiality and some loss of integrity.

References

Community reviews

Loading reviews…