CVE-2026-21410
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedInSAT 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceInSAT MasterSCADA BUK-TS contains a SQL Injection vulnerability in its main web interface. An unauthenticated or authenticated malicious user can inject arbitrary SQL queries through the vulnerable endpoint, potentially escalating to operating system command execution and remote code execution on the host system.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE dataall versionsCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm MasterSCADA installationLook for MasterSCADA software on the system - check installed programs in Control Panel or program directories (e.g., C:\Program Files\InSAT\MasterSCADA or similar paths depending on installation)Affected if MasterSCADA software is present on the system
-
Verify BUK-TS web service is runningCheck if the BUK-TS web service/process is active - look for related services in Windows Services or check running processes for MasterSCADA web componentsAffected if The BUK-TS web interface service is running or enabled
-
Check web interface network exposureIdentify ports used by the web interface (typically ports 8080, 80, 443 or custom ports) and determine if they are accessible from network locations - use netstat or port scanning toolsAffected if The web interface is accessible from network locations beyond localhost
-
Identify web interface endpointsProbe the web server for accessible URLs and endpoints - check if unauthenticated access to SQL-facing forms or parameters is possibleAffected if Unauthenticated web endpoints that accept user input are exposed without additional access controls
If MasterSCADA with the BUK-TS web interface is installed and the web interface is network-accessible, the system is affected by this SQL injection vulnerability.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply vendor-supplied patch or update to MasterSCADA BUK-TS. If no patch available, restrict network access to the web interface, implement web application firewall rules, and validate all user inputs before database queries.
- Consultation12.0 h
- Implementation24.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $16,896.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-21410 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-21410 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data