Skip to main content
CVE-2025-3091VulnerabilityPublished

CVE-2025-3091: MB connect line mbCONNECT24 · Insecure Direct Object Reference

Affects MB connect line mbCONNECT24Source CVE Database V5

0

Not known to be exploited · CVSS 7.5 High.

Data as of 25 Oct 2026, 19:02 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Jun 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 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
MB connect line mbCONNECT24Affected
  • =0
Fixed in–

AI-suggested

1. Immediate mitigation should include enforcing strict control and monitoring of second-factor devices or tokens to prevent unauthorized possession. 2. Implement additional authentication layers or anomaly detection systems to identify unusual login patterns or simultaneous logins from different locations. 3. Restrict remote access to mbCONNECT24 interfaces via network segmentation, VPNs, or IP whitelisting to reduce exposure. 4. Conduct thorough user education and awareness campaigns emphasizing the importance of safeguarding second-factor credentials. 5. Monitor logs for suspicious authentication attempts and implement alerting mechanisms. 6. Engage with MB connect line for timely updates and patches; prioritize patch deployment once available. 7. Consider temporary disabling or limiting use of second-factor authentication methods vulnerable to theft or duplication until a fix is applied. 8. Review and tighten authorization policies within mbCONNECT24 to ensure that possession of a second factor alone cannot grant access without password verification.

Description

An low privileged remote attacker in possession of the second factor for another user can login as that user without knowledge of the other user`s password.

References

Community reviews

Loading reviews…