Scada-LTS DWR Authorization Bypass - Systemic
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Scada-LTS | Scada-LTS | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Scada-lts | Scada-lts |
|
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.482% probability within 30 days)
| Link | Providers |
|---|---|
| https://www.tenable.com/security/research/tra-2026-60 |
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Scada-lts
Scada-lts scada-lts |
|
| Vendors & Products |
Scada-lts
Scada-lts scada-lts |
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-639 | |
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | ScadaLTS 2.8.1-release-candidate build 0 is affected by an Authorization Bypass Spring Security gates DWR endpoints by URL path pattern, but DWR itself dispatches method calls based on the POST body parameters c0-scriptName and c0-methodName. The crossDomainSessionSecurity setting in web.xml is set to false, which disables DWR's built-in origin validation. This means any authenticated user can invoke any DWR method (regardless of the URL-based access control) by sending their request to a URL they are permitted to access (e.g. MiscDwr.initializeLongPoll.dwr) while targeting a restricted class in the POST body. This is the systemic root cause that enables multiple other findings to be exploited as a low privilege user. | |
| Title | Scada-LTS DWR Authorization Bypass - Systemic | |
| References |
| |
| Metrics |
cvssV3_1
|