Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain low-privilege Scada-LTS credentials
-
DeliveryReach DWR endpoint via routing bypass
-
ExploitInvoke DataSourceEditDwr.validateScript with malicious JS
-
ExecutionRhino compiles and executes payload
-
ImpactAchieve remote code execution on server
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Code injection prevention, sandbox exec
MITRE ATT&CK
2 techniques across 2 tactics: Execution, Initial Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires a valid low-privilege Scada-LTS user account (per CVSS PR:L and the description's 'access to a low privilege user'), and network reachability to the application's DWR interface. The specific trigger is the DataSourceEditDwr.validateScript DWR method, which performs no authorization check and is reachable via a DWR routing bypass, then compiles and executes the supplied JavaScript through the Rhino engine. No user interaction and no non-default configuration are needed - the vulnerable method is exposed by the standard build (2.8.1-release-candidate build 0). The primary limiting factor is authentication: an attacker must first hold or obtain credentials for any account; instances not exposed to the attacker's network and instances requiring MFA/hardened access are correspondingly harder to reach. |
| Impact | This is a genuine, credible priority rather than an inflated high-CVSS artifact. The vendor CVSS of 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) is well-aligned with the described mechanism: a network-reachable DWR endpoint (DataSourceEditDwr.validateScript) that compiles and runs attacker-supplied JavaScript through the Rhino engine, yielding code execution on the server. The PR:L rating is consistent with the description's 'authenticated ... low privilege user' framing, and the 'DWR routing bypass' plus absence of authorization checks on the method mean even a low-privilege account escalates directly to RCE - a large real-world jump. Signals are thin but not conflicting: no EPSS score, no CISA KEV entry, and no public POC are present in the input, so there is no evidence of active exploitation or mass automation. The finding is from Tenable research (TRA-2026-60), a reputable source, which raises confidence in the technical accuracy even though it lowers the likelihood of opportunistic mass exploitation. Net: treat as a high-priority patch/mitigation target for any exposed Scada-LTS instance because impact is full server compromise and complexity is low, while acknowledging exploitation currently appears to require valid low-privilege credentials and there is no confirmed in-the-wild activity. |
| Exploit ScenarioDerived | An attacker who has obtained any low-privilege Scada-LTS account (or credentials via phishing/reuse) sends a crafted DWR request to the DataSourceEditDwr.validateScript method, supplying malicious JavaScript that the Rhino engine compiles and executes on the server, achieving remote code execution in the application's context. Because the method lacks authorization checks and is reachable through a DWR routing bypass, the low-privilege role restriction is meaningless. No public exploit code is identified in the provided data, though Tenable's advisory (TRA-2026-60) documents the technique in detail. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 16, 2026
Authenticated remote code execution in ScadaLTS 2.8.1-release-candidate build 0 allows any holder of a low-privilege account to run arbitrary JavaScript on the server by abusing the scripting sandbox. The DWR-exposed DataSourceEditDwr.validateScript method performs no authorization check and is reachable through a DWR routing bypass, so supplied code is compiled and executed by the Rhino engine with the application's privileges (CVSS 3.1: 8.8, AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). There is no public exploit identified at time of analysis and no confirmed actively exploited (CISA KEV) status; the independent assessment treats this as a genuine, credible priority rather than an inflated high-CVSS artifact, with the requirement for valid credentials being the principal limiting factor.
RemediationAI
No vendor-released patch identified at time of analysis, and the provided references point only to research and tracking advisories (https://www.tenable.com/security/research/tra-2026-60 and https://nvd.nist.gov/vuln/detail/CVE-2026-84858) rather than a fixed release; confirm current ScadaLTS release notes before assuming an upgrade resolves the issue. Until a fix is published, apply compensating controls: block or remove the DataSourceEditDwr.validateScript DWR endpoint at a reverse proxy or WAF by rejecting POSTs to the /dwr/ paths that invoke DataSourceEditDwr while allowing other DWR traffic - the trade-off is that legitimate data-source script validation in the admin UI will stop working, and any rule must be maintained against future DWR call-name encoding variations given the routing bypass. If scripting-based data sources are not used, disable the Rhino scripting feature or remove the scripting/data-source editing privilege from all non-administrative roles so a low-privilege account - the sole prerequisite for exploitation - no longer reaches the method. Restrict network access to the ScadaLTS web interface to trusted management networks or VPN with MFA, since the exploit requires only a valid low-privilege login and no user interaction, and audit existing accounts for unauthorized or stale low-privilege users that could serve as the entry point. Monitoring should focus on anomalous POST requests to DWR endpoints and on outbound connections or child processes spawned by the ScadaLTS JVM, which would indicate successful command execution through the embedded script engine.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
ScadaLTS is a Java-based supervisory control and data acquisition (SCADA) web application whose front end relies on DWR (Direct Web Remoting), a framework that exposes server-side Java methods to browser JavaScript over HTTP under paths such as /dwr. The vulnerable class, DataSourceEditDwr, publishes a validateScript method that takes attacker-controlled script text, hands it to the embedded Mozilla Rhino JavaScript engine for compilation, and executes it. Two defects combine here: the method lacks any authorization or role check despite living in an administrative data-source editing surface, and it can be reached through a DWR routing bypass that circumvents the normal access-control path. The provided feeds carry no CWE assignment; as an analyst mapping, the behavior corresponds to a missing-authorization class (CWE-862-style) combined with code injection through an embedded scripting engine (CWE-94-style), where Rhino's sandbox is assumed to constrain the script but does not prevent server-side code execution. The CPE string cpe:2.3:a:scada-lts:scada-lts:*:*:*:*:*:*:*:* uses a wildcard version and therefore matches broadly, while EUVD narrows the reported affected release to Scada-LTS 2.8.1 and the description fixes the tested build at 2.8.1-release-candidate build 0.
Know when Scada Lts gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Network-reachable DWR method, low complexity, requires a low-privilege authenticated account (PR:L), and server-side code execution yields full confidentiality, integrity, and availability impact.
Primary rating from Vendor (tenable).
CVSS VectorVendor: tenable
DescriptionCVE.org
ScadaLTS 2.8.1-release-candidate build 0 is affected by an Authenticated Remote Code Execution via Scripting Sandbox Bypass
The DWR "DataSourceEditDwr" class exposes the "validateScript" method that compiles and executes attacker-supplied JavaScript via the Rhino scripting engine. There are no authorization checks on this method and so it is possible for an attacker with access to a low privilege user to abuse this flaw by leveraging the DWR routing bypass.
Executive ViewAI
ScadaLTS 2.8.1-release-candidate build 0 contains an authenticated remote code execution vulnerability that allows a low-privilege user to execute arbitrary code on the server, putting industrial monitoring and control operations at risk of unauthorized manipulation or disruption. No vendor-released patch identified at time of analysis and no public exploit identified at time of analysis; however, the combination of authenticated access and SCADA deployment makes this a credible high-priority issue for OT/ICS leadership. Organizations running this exact build should reduce exposure and privilege immediately while preparing to migrate to a supported release.
No vendor-released patch identified at time of analysis. Interim mitigations include disabling or blocking DWR endpoints, especially DataSourceEditDwr.validateScript, and the scripting sandbox where feasible; restricting network access to ScadaLTS and segmenting OT networks; enforcing least privilege and MFA; deploying WAF or reverse-proxy rules to block DWR routing bypass and validateScript requests; monitoring for unauthorized script compilation or execution; and applying a vendor patch when available.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Code injection occurs when an application accepts user input and passes it directly into a language interpreter or evaluator without proper sanitization.
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
An issue was discovered in Scada-LTS v2.7.5.2 build 4551883606 and before, allows remote attackers with low-level authen
Privileged remote code execution in ScadaLTS 2.7.8.1 lets any authenticated user - including accounts holding only low-p
Authorization bypass in ScadaLTS 2.8.1-release-candidate build 0 lets any authenticated user invoke restricted DWR metho
Authenticated blind SQL injection in ScadaLTS 2.8.1-release-candidate build 0 lets any logged-in user with the lowest pr
Reflected cross-site scripting in ScadaLTS 2.7.8.1 enables an unauthenticated remote attacker to execute arbitrary JavaS
A vulnerability was identified in Scada-LTS up to 2.7.8.1. Rated medium severity (CVSS 5.3), this vulnerability is remot
A vulnerability was determined in Scada-LTS up to 2.7.8.1. Rated medium severity (CVSS 5.3), this vulnerability is remot
A vulnerability was determined in Scada-LTS 2.7.8.1. Rated medium severity (CVSS 5.3), this vulnerability is remotely ex
Stored cross-site scripting (XSS) in Scada-LTS up to version 2.7.8.1 allows authenticated remote attackers to inject mal
Stored cross-site scripting (XSS) in Scada-LTS up to 2.7.8.1 allows authenticated users to inject malicious scripts via
A vulnerability has been found in Scada-LTS 2.7.8.1. Rated medium severity (CVSS 5.1), this vulnerability is remotely ex
A vulnerability was determined in Scada-LTS up to 2.7.8.1. Rated medium severity (CVSS 5.1), this vulnerability is remot
EUVD-2026-80825
GHSA-mrrr-7mg7-864j
NVD
CVE.org
EPSS
Exploit-DB