Skip to content
Fencer Intel
high 7.2

CVE-2026-6888 json

SQL Injection Vulnerability

published 5mo ago modified 16d ago also EUVD-2026-29896

cvss
7.2
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 31%
public exploits
0
none known

Summary

Successful exploitation of the SQL injection vulnerability could allow a remote authenticated attacker to execute arbitrary commands via a specific interface, potentially enabling the attacker to access, modify, or delete sensitive information within the database.

Is CVE-2026-6888 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
5mo ago

Exploit prediction

0.38% chance of exploitation in the next 30 days, higher than 31% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by version score vector
CNA 3.1 7.2 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Affected products

  • Advantech SaaS Composer
  • Advantech IoTSuite Growth Linux docker
  • Advantech IoTSuite Starter Linux docker
  • Advantech IoT Edge Linux docker
  • Advantech IoT Edge Windows
  • Advantech WebAccess/SCADA
  • Advantech WebAccess SaaS-Composer
  • Advantech ECOWatch SaaS-Composer

Classification

Weakness
  • CWE-89 Improper Neutralization of Special Elements used in an SQL Command

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.