ScadaLTS 2.8.1-release-candidate build 0 Search Endpoint spring-security.xml sortBy sql injection

Summaryinfo

A vulnerability has been found in ScadaLTS 2.8.1-release-candidate build 0 and classified as critical. Affected by this issue is some unknown functionality of the file spring-security.xml of the component Search Endpoint. The manipulation of the argument sortBy leads to sql injection. This vulnerability is traded as CVE-2026-84859. It is possible to initiate the attack remotely. There is no exploit available.

Detailsinfo

A vulnerability was found in ScadaLTS 2.8.1-release-candidate build 0. It has been rated as critical. This issue affects an unknown part of the file spring-security.xml of the component Search Endpoint. The manipulation of the argument sortBy with an unknown input leads to a sql injection vulnerability. Using CWE to declare the problem leads to CWE-89. The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

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.

The advisory is shared at tenable.com. The identification of this vulnerability is CVE-2026-84859 since 09/02/2026. The exploitation is known to be easy. The attack may be initiated remotely. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 09/16/2026). MITRE ATT&CK project uses the attack technique T1505 for this issue.

By approaching the search of inurl:spring-security.xml it is possible to find vulnerable targets with Google Hacking.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• SCADA Software

Name

• ScadaLTS

Version

• 2.8.1-release-candidate build 0

CPE 2.3info

• 🔒

CPE 2.2info

• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion