Skip to main content
VulnerabilityPublished Updated

CVE-2025-41674: MB connect line mbNET.mini · OS Command Injection

Affects MB connect line mbNET.miniSource CVE Database V5

0

Not known to be exploited · CVSS 7.2 High.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
7.2High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.7% 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:H/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 implement network segmentation to isolate mbNET.mini devices from untrusted networks and limit access to trusted administrators only.
  2. Enforce strict access controls and monitor for unusual POST requests targeting diagnostic functions.
  3. Use VPNs or secure tunnels for remote access to reduce exposure to direct network attacks.
  4. Regularly audit and rotate credentials to minimize the risk of privilege escalation.
  5. Apply any available vendor patches or firmware updates as soon as they are released.
  6. Employ intrusion detection systems (IDS) with signatures or heuristics to detect command injection attempts.
  7. Conduct thorough security assessments of the mbNET.mini deployment environment to identify and remediate other potential vulnerabilities.
  8. Develop incident response plans specifically addressing potential exploitation scenarios involving these devices.
  9. Engage with MB connect line support channels to obtain updates and guidance on mitigation strategies.
  10. Consider compensating controls such as disabling diagnostic POST functionalities if feasible until patches are available.

Description

A high privileged remote attacker can execute arbitrary system commands via POST requests in the diagnostic action due to improper neutralization of special elements used in an OS command.

References

Community reviews

Loading reviews…