CVE-2026-6888
SQL Injection Vulnerability
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: no
- Technical impact: total
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Advantech SaaS Composer
prior to version 3.4.17
- Advantech IoTSuite Growth Linux docker
prior to version 2.2.0
- Advantech IoTSuite Starter Linux docker
prior to version 2.2.0
- Advantech IoT Edge Linux docker
prior to version 2.2.0
- Advantech IoT Edge Windows
prior to version 2.2.0
- Advantech WebAccess/SCADA
prior to version 9.2.3
- Advantech WebAccess SaaS-Composer
prior to version 3.4.17.1
- Advantech ECOWatch SaaS-Composer
prior to version 3.4.17