Quick answers
- Is CVE-2026-84860 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-84860 being exploited in the wild.
- How severe is CVE-2026-84860?
- High severity, with a CVSS score of 8.8, published 16 September 2026.
- Which products and versions are affected?
- ScadaLTS 2.8.1-release-candidate build 0.
- Is there a fix for CVE-2026-84860?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-84860 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-84860?
- Check whether you run ScadaLTS at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
ScadaLTS uses Spring Security to gate DWR (Direct Web Remoting) endpoints by URL path pattern, but DWR dispatches method calls based on POST body parameters (c0-scriptName and c0-methodName) instead of the URL. The crossDomainSessionSecurity setting in web.xml is disabled, removing DWR's built-in origin validation. Any authenticated user can invoke any DWR method by sending requests to a URL they have permission to access while specifying a restricted class in the POST body parameters. This systemic bypass enables low-privilege users to exploit other vulnerabilities (such as arbitrary code execution and SQL injection) that would otherwise require elevated privileges. No patch information is currently available as of the advisory publication date.
Affected products
- ScadaLTS ScadaLTS 2.8.1-release-candidate build 0
Timeline
- 2026-09-16: disclosed