# CVE-2026-40455: SQL Injection in LMS

> Authenticated attackers can exploit SQL injection in LMS to extract sensitive database information via the tarifflist.php module.

- **Severity:** High 8.6 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Jun 2026
- **Updated:** 18 Jun 2026
- **Also known as:** GHSA-qrw9-xj5g-qxw8

## What is CVE-2026-40455?

CVE-2026-40455 is a high-severity SQL injection vulnerability in LMS, published on 18 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An SQL Injection vulnerability exists in LMS (LAN Management System) before commit 4cb30a7 within the "tarifflist.php" module due to insufficient sanitization of the POST "tg[]" parameter. The application directly concatenates user-supplied array values into an SQL query using "implode()", allowing authenticated attackers to perform Error-Based SQL injection and extract sensitive database information.

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

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


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

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

## Is CVE-2026-40455 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-40455 is a high-severity SQL injection vulnerability in LMS, published on 18 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-40455 in the wild and no public exploit code.

Affected product: LMS. 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-40455/ (Markdown: https://insights.sbomify.com/CVE-2026-40455/index.md)
```

## Sources

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

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