CVE
Authenticated SQL injection in getVpnData function
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Not reported
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.29% · 22nd percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 15/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The getVpnData function in the MB connect line mbCONNECT24 and mymbCONNECT24 products, and the Helmholz myREX24V2 and myREX24V2.virtual products, has an SQL injection flaw. A remote attacker with high-level privileges can reach it over the network and use it to read database data, causing a total loss of confidentiality.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
A high privileged remote attacker can exploit an unauthenticated SQL Injection vulnerability in the getVpnData function due to improper neutralization of special elements in a SQL SELECT command. This can result in a total loss of confidentiality.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity6.9/10CVSS 6.9
- No patch5/5No patch listed yet
What would change the score
- Would score about 70 if added to CISA KEV
- Would score about 65 if CISA's SSVC rates exploitation active
- Would score about 34 if advisories confirm default setups are exposed
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-40820 (Authenticated SQLi in getVpnData function), 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-40820 (entry last updated 2026-11-12):
Affected:
- MB connect line mbCONNECT24: from 1.0.0, through 2.20.0
- MB connect line mymbCONNECT24: from 1.0.0, through 2.20.0
- MB connect line mbCONNECT24: versions 2.20.0
- MB connect line mymbCONNECT24: versions 2.20.0
- Helmholz myREX24V2: from 1.0.0, through 2.20.0
- Helmholz myREX24V2.virtual: from 1.0.0, through 2.20.0
- Helmholz myREX24V2: versions 2.20.0
- Helmholz myREX24V2.virtual: versions 2.20.0
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-40820 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-40820 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-044/
- https://www.certvde.com/en/advisories/VDE-2026-058/
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-40820
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-40820"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- MB connect line mbCONNECT24
From 1.0.0 · through 2.20.0
- MB connect line mymbCONNECT24
From 1.0.0 · through 2.20.0
- MB connect line mbCONNECT24
2.20.0
- MB connect line mymbCONNECT24
2.20.0
- Helmholz myREX24V2
From 1.0.0 · through 2.20.0
- Helmholz myREX24V2.virtual
From 1.0.0 · through 2.20.0
- Helmholz myREX24V2
2.20.0
- Helmholz myREX24V2.virtual
2.20.0
Evidence 4
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 2
- Link
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-40820
Is CVE-2026-40820 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: cve.now feed data
Which versions are affected by CVE-2026-40820?
mbCONNECT24: from 1.0.0 through 2.20.0. mymbCONNECT24: from 1.0.0 through 2.20.0. mbCONNECT24: version 2.20.0. mymbCONNECT24: version 2.20.0. myREX24V2: from 1.0.0 through 2.20.0. 3 more packages are listed on the page.Source: cve.now feed data