CVE-2026-8604

ScadaBR · ScadaBR

ScadaBR version 1.2.0 is vulnerable to a Cross-Site Request Forgery (CSRF) attack, which allows unauthorized actors to execute actions on behalf of an authenticated user.

Executive summary

A high-severity Cross-Site Request Forgery (CSRF) vulnerability in ScadaBR 1.2.0 poses a significant risk to industrial control environments, as it is currently being actively exploited in the wild.

Vulnerability

This is a Cross-Site Request Forgery (CWE-352) vulnerability that allows a remote attacker to trick an authenticated user into performing unintended actions within the application. Because the application fails to validate the origin of requests, an attacker can manipulate a logged-in user into executing administrative or operational commands.

Business impact

The exploitation of this vulnerability carries a CVSS score of 8.8, indicating a high risk of unauthorized state changes within industrial control systems. Successful exploitation could lead to operational disruption, unauthorized manipulation of critical infrastructure, and severe compromise of system integrity. Given that the software is used in industrial environments, the potential for real-world physical or process impact is substantial.

Remediation

Immediate Action: Review the official CISA advisory (ICSA-26-139-03) for the latest available patches or configuration changes provided by ScadaBR. If a patch is not yet available, restrict access to the ScadaBR interface to trusted networks only.

Proactive Monitoring: Monitor network traffic and application access logs for anomalous request patterns originating from external sources or unexpected user sessions.

Compensating Controls: Deploy a Web Application Firewall (WAF) to enforce strict referer header checks and implement CSRF tokens where possible to block unauthorized cross-site requests.

Exploitation status

Public Exploit Available: true

Analyst recommendation

Due to the confirmed active exploitation of this vulnerability in industrial environments, organizations must treat this as a top-priority security event. Security teams should isolate affected systems from the public internet immediately and apply all vendor-recommended patches as soon as they are released to prevent unauthorized operational interference.