Skip to content
major vulnerability· requires attention

Unauthenticated SQL injection in a SCADA product can lead to database compromise and disruption of critical industrial systems; high-impact to OT environments.

IoT

CVE-2026-16462

9.3
Critical
EPSS 0.48%Patch availableJul 28, 2026

Unauthenticated SQL injection in PROCON-WEB SCADA GetGridData endpoint.

common questions

Is CVE-2026-16462 being exploited?

Not confirmed. CVE-2026-16462 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.48% probability of exploitation in the next 30 days.

How severe is CVE-2026-16462?

CVE-2026-16462 is rated Critical with a CVSS score of 9.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-16462?

Yes. A fix has been recorded for CVE-2026-16462. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-16462 affect?

CVE-2026-16462 affects PROCON-WEB SCADA, GetGridData endpoint. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-16462?

Isolate SCADA, block access to endpoint, deploy WAF rules, monitor logs, apply vendor patch when released.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
PROCON-WEB SCADAGetGridData endpoint
impact

Remote unauthenticated SQL injection allows arbitrary SQL execution: data theft, DB compromise, manipulation of control data and potential lateral movement into ICS.

action required

Immediate action required

affected versions
Weidmueller Interface PROCON-WEB SCADA
  • affected>= 1.0.0 and <= 6.11.2

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free