mbCONNECT24: Improper Neutralization of Special Elements used in an OS Command
CVE-2026-60036 is a high-severity improper neutralization of special elements used in an OS command vulnerability in mbCONNECT24 from MB connect line, with a CVSS 3.1 base score of 7.2 out of 10. It can be exploited remotely over the network by an attacker with administrator privileges, without any action from a user. The record lists version 2.21.0 as the first without the flaw, so updating mbCONNECT24 to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.49% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update mbCONNECT24 to 2.21.0 or a later version.
- Update mymbCONNECT24 to 2.21.0 or a later version.
- Update myREX24V2 to 2.21.0 or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| MB connect line | mbCONNECT24 | 2.0.0 up to, but not including, 2.21.0 | 2.21.0 |
| MB connect line | mymbCONNECT24 | 2.0.0 up to, but not including, 2.21.0 | 2.21.0 |
| Helmholz | myREX24V2 | 2.0.0 up to, but not including, 2.21.0 | 2.21.0 |
| Helmholz | myREX24V2.virtual | 2.0.0 up to, but not including, 2.21.0 | 2.21.0 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- HighAdministrator-level access is required first.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H. Scored by CNA (cert.vde.com).
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 4.0 | 8.6 | High | CNA (cert.vde.com) |
| CVSS 3.1 | 7.2 | High | CNA (cert.vde.com) |
Official description
A high privileged remote attacker can perform a code injection in the backends patch activate function leading to code execution. This can result in a total loss of confidentiality, integrity and availability.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Neutralization of Special Elements used in an OS Command
The product constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command before it is sent to a downstream component.
How developers prevent this class of flaw
- If at all possible, use library calls rather than external processes to recreate the desired functionality.
- For any data that will be used to generate a command to be executed, keep as much of that data out of external control as possible. For example, in web applications, this may require storing the data locally in the session's state instead of sending it out to the client in a hidden form field.
- For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.
More Improper Neutralization of Special Elements used in an OS Command vulnerabilities (CWE-78)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Other vulnerabilities in mbCONNECT24
- 7.5 High severity
- 7.5 High severity
- 9.3 Critical severity
- 8.1 High severity
- 7.2 High severity
- 7.2 High severity
Recent Improper Neutralization of Special Elements used in an OS Command vulnerabilities
- 7.8 High severity
- 8.0 High severity
- 8.4 High severity
- 7.0 High severity
- 7.2 High severity
- 8.8 High severity
Spotted an error? Tell us.