# CVE-2026-84859: Scada-LTS Authenticated Blind SQL Injection

> Authenticated users can exploit blind SQL injection in Scada-LTS to extract arbitrary database data, including password hashes.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Sep 2026
- **Updated:** 17 Sep 2026
- **Also known as:** GHSA-gqpm-g63c-92xv

## What is CVE-2026-84859?

CVE-2026-84859 is a medium-severity SQL injection vulnerability in Scada-LTS, published on 16 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

ScadaLTS 2.8.1-release-candidate build 0 is affected by an Authenticated Blind SQL Injection

The /api/events/search endpoint accepts a JSON body containing a sortBy array. The values in this array are concatenated directly into the SQL ORDER BY clause without any sanitization or parameterization. This allows authenticated users with the ROLE_USER role to perform time-based and boolean-based blind SQL injection to extract arbitrary data from the database, including password hashes of all users.

The endpoint is accessible to any authenticated user with ROLE_USER, ROLE_ADMIN, or ROLE_PUBLIC via POST /api/events/search as defined in spring-security.xml.

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

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


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

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

## Is CVE-2026-84859 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-84859 is a medium-severity SQL injection vulnerability in Scada-LTS, published on 16 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-84859 in the wild and no public exploit code.

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

## Sources

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

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