CVE-2026-60042MB connect line mbCONNECT24 insecure direct object reference
CVE-2026-60042 is a insecure direct object reference in MB connect line mbCONNECT24, rated medium (6.9 on CVSS 4.0).
Why this priority: Medium severity, with no exploitation signal.
Published · Updated · NVD status: Received
What it is
Changing an identifier in a request reaches another user's records.
How it is reached
An attacker can exploit it over the network, without an account, and nobody has to click anything.
What an attacker gains
The scored direct impact on the component itself is low. In practice, this kind of flaw lets an attacker reach data or actions their role should not allow. The damage can spread past the vulnerable component into others.
Is it being exploited?
There is no public report of exploitation yet. It can be exploited automatically, at scale.
What to do
- Upgrade MB connect line mbCONNECT24 to 2.21.0 or later. Other affected products have their own fixed versions on this page.
- Until it is patched, keep it off the internet or behind a VPN, allowlist or authenticating proxy.
Description from NVD
An unauthenticated remote attacker can perform an authentication bypass on the com_check function, potentially triggering traffic on other systems and email alerts. This can result in some loss of availability due to higher system loads.
What this means for your architecture.
A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.
Components it touches
- Permission checks in APIs and admin surfaces. The flaw sits between one role or tenant and another.
- Multi-tenant services. The flaw sits between one role or tenant and another.
Trust boundaries in play
- Internet-facing entry points. No account is needed. Any instance reachable from outside your perimeter, through a load balancer, gateway, VPN or exposed admin port, is in scope.
- Isolation between components. The impact crosses out of the vulnerable component into others it should be isolated from.
- Between one role or tenant and another. An attacker who crosses it can reach data or actions their role should not allow.
Questions to answer about your own systems
- Where does MB connect line mbCONNECT24 run in your systems, and at which version?
- Which of those instances can be reached from the internet or partner networks?
- What can it reach once compromised: which data stores, secrets and services?
Sources
- CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
- Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
- Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
- Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.