# CVE-2026-40816: Unauthenticated SQLi in _mb24confi_getTagAlarm function

> Unauthenticated attackers can exploit SQL injection in mbCONNECT24 to read sensitive data, requiring immediate attention from users of Helmholz and MB connect line products.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 May 2026
- **Updated:** 27 May 2026
- **Also known as:** GHSA-7845-cw4c-743q

## What is CVE-2026-40816?

CVE-2026-40816 is a high-severity SQL injection vulnerability in Helmholz mbCONNECT24, published on 27 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An unauthenticated remote attacker can exploit an unauthenticated SQL Injection vulnerability in the mb24alarm.php files _mb24confi_getTagAlarm function due to improper neutralization of special elements in a SQL SELECT command. This can result in a total loss of confidentiality.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2026-40816?


## How do I fix CVE-2026-40816?

No fix has been published for CVE-2026-40816 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-40816 being exploited?

There is no known exploitation of CVE-2026-40816 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-40816 and fix it if it is affected.

What it is: CVE-2026-40816 is a high-severity SQL injection vulnerability in Helmholz mbCONNECT24, published on 27 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-40816 in the wild and no public exploit code.

Affected product: Helmholz mbCONNECT24. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-40816/ (Markdown: https://insights.sbomify.com/CVE-2026-40816/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-40816
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-40816
- OSV: https://osv.dev/vulnerability/CVE-2026-40816

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-40816/
Summaries are generated and may contain mistakes; the official description above is the record.