CVE-2025-9143: Scada-LTS · Cross Site Scripting
Affects Scada-LTSSource CVE Database V5
Not known to be exploited · CVSS 5.1 Medium.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 31% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:PExploitation evidence
Disclosed: evidence found.
CVE published 19 Aug 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Scada-LTS | Affected
| Fixed in– |
AI-suggested
1. Immediate patching: Organizations should monitor for official patches or updates from the Scada-LTS project addressing this vulnerability and apply them promptly once available. 2. Input validation and sanitization: Until a patch is released, implement web application firewalls (WAFs) or reverse proxies with custom rules to detect and block suspicious input patterns targeting the name, userList, and address parameters. 3. User awareness and training: Educate users with access to the SCADA interface about the risks of clicking unknown links or interacting with untrusted content to reduce the likelihood of successful XSS exploitation. 4. Segmentation and access control: Restrict access to the SCADA-LTS management interface to trusted networks and users only, employing VPNs and multi-factor authentication to reduce exposure. 5. Monitoring and logging: Enhance logging of web interface activities and monitor for anomalous behavior indicative of XSS exploitation attempts, such as unusual parameter values or repeated failed access attempts. 6. Content Security Policy (CSP): Where possible, implement CSP headers to limit the execution of unauthorized scripts within the SCADA web interface. 7. Incident response readiness: Prepare to respond to potential exploitation by having procedures in place to isolate affected systems and conduct forensic analysis.
Description
A security flaw has been discovered in Scada-LTS 2.7.8.1. This affects an unknown part of the file mailing_lists.shtm. The manipulation of the argument name/userList/address results in cross site scripting. It is possible to launch the attack remotely. The exploit has been released to the public and may be exploited.