Skip to main content
VulnerabilityPublished Updated

CVE-2025-41678: MB connect line mbNET.mini · SQL Injection

Affects MB connect line mbNET.miniSource CVE Database V5

0

Not known to be exploited · CVSS 6.5 Medium.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 52% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Jul 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: 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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
MB connect line mbNET.miniAffected
  • =0.0.0
Fixed in–

AI-suggested

  1. Immediately restrict remote access to mbNET.mini devices to trusted networks and users only, employing network segmentation and firewall rules to limit exposure.
  2. Implement strong authentication and credential management practices to prevent unauthorized privilege escalation.
  3. Monitor and log POST requests to the device’s configuration interface for unusual or malformed inputs indicative of injection attempts.
  4. Deploy intrusion detection or prevention systems capable of identifying SQL injection patterns targeting industrial devices.
  5. Engage with MB connect line vendor support to obtain patches or firmware updates as soon as they become available and apply them promptly.
  6. Conduct regular security audits and penetration tests focusing on industrial control system components to identify and remediate similar vulnerabilities.
  7. Educate operational technology staff on the risks of SQL injection and the importance of secure configuration management.
  8. Consider implementing application-layer gateways or proxies that sanitize inputs before they reach the device if immediate patching is not feasible.

Description

A high privileged remote attacker can alter the configuration database via POST requests due to improper neutralization of special elements used in a SQL statement.

References

Community reviews

Loading reviews…