Skip to main content
CVE-2026-21410VulnerabilityPublished Updated

CVE-2026-21410: InSAT MasterSCADA BUK-TS · SQL Injection

Affects InSAT MasterSCADA BUK-TSSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 49% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Feb 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
InSATMasterSCADA BUK-TSAffected
  • =All versions
Fixed in–

AI-suggested

Given the absence of official patches, organizations should immediately implement the following specific mitigations: 1) Restrict network access to the MasterSCADA BUK-TS web interface by isolating it within secure network segments and enforcing strict firewall rules to limit exposure to trusted IP addresses only. 2) Deploy web application firewalls (WAFs) with custom rules to detect and block SQL injection patterns targeting the vulnerable endpoints. 3) Conduct thorough input validation and sanitization on any user-supplied data if custom integrations or extensions exist. 4) Monitor logs and network traffic for unusual database queries or signs of exploitation attempts. 5) Implement multi-factor authentication and strong access controls around SCADA management interfaces to reduce attack surface. 6) Prepare incident response plans specifically addressing potential SCADA compromises. 7) Engage with the vendor for timely updates and patches, and plan for rapid deployment once available. 8) Consider temporary shutdown or replacement of vulnerable systems in high-risk environments if mitigation controls are insufficient.

Description

InSAT MasterSCADA BUK-TS is susceptible to SQL Injection through its main web interface. Malicious users that use the vulnerable endpoint are potentially able to cause remote code execution.

References

Community reviews

Loading reviews…