IoTSuite and IoT Edge Products: Improper Neutralization of Special Elements used in an SQL Command
CVE-2025-52694 is a critical-severity improper neutralization of special elements used in an SQL command vulnerability in IoTSuite and IoT Edge Products from Advantech, with a CVSS 3.1 base score of 9.8 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected IoTSuite and IoT Edge Products versions: SaaSComposer prior to version V3.4.15; IoTSuite Growth Linux docker prior to version V2.0.2; IoTSuite Starter Linux docker prior to version V2.0.2, and others listed below. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 39.9% chance of exploitation within 30 days, which is in the top 1.35% of all scored CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Update IoT Edge Linux Docker to 2.0.2 or a later version.
- Update IoT Edge Windows to 2.0.2 or a later version.
- Update Iotsuite Growth Linux Docker to 2.0.2 or a later version.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Advantech | IoTSuite and IoT Edge Products | SaaSComposer prior to version V3.4.15; IoTSuite Growth Linux docker prior to version V2.0.2; IoTSuite Starter Linux docker prior to version V2.0.2; IoT Edge Linux docker prior to version V2.0.2; IoT Edge Windows prior to version V2.0.2; WebAccess/SCADA prior to version V9.2.2; WebAccess SaaS-Composer prior to version 3.4.15.1; ECOWatch SaaS-Composer prior to version 3.4.15 | Not stated |
| Advantech | IoT Edge Linux Docker | before 2.0.2 | 2.0.2 |
| Advantech | IoT Edge Windows | before 2.0.2 | 2.0.2 |
| Advantech | Iotsuite Growth Linux Docker | before 2.0.2 | 2.0.2 |
| Advantech | Iotsuite Saas Composer | before 3.4.15 | 3.4.15 |
| Advantech | Iotsuite Starter Linux Docker | before 2.0.2 | 2.0.2 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 10.0 | Critical | CNA |
| CVSS 3.1 | 9.8 | Critical | NVD |
Official description
Successful exploitation of the SQL injection vulnerability could allow an unauthenticated remote attacker to execute arbitrary SQL commands on the vulnerable service when it is exposed to the Internet, potentially affecting data confidentiality, integrity, and availability. Users and administrators of affected product versions are advised to update to the latest versions immediately.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Neutralization of Special Elements used in an SQL Command
The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.
How developers prevent this class of flaw
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, consider using persistence layers such as Hibernate or Enterprise Java Beans, which can provide significant protection against SQL injection if used properly.
- For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.
- When the set of acceptable objects, such as filenames or URLs, is limited or known, create a mapping from a set of fixed input values (such as numeric IDs) to the actual filenames or URLs, and reject all other inputs.
More Improper Neutralization of Special Elements used in an SQL Command vulnerabilities (CWE-89)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
- csa.gov.sg/alerts-and-advisories/alerts/alerts-al-2026-001/Mitigation, Third Party Advisory
Recent Improper Neutralization of Special Elements used in an SQL Command vulnerabilities
- 9.4 Critical severity
- 9.1 Critical severity
- 8.7 High severity
- 9.8 Critical severity
- 10.0 Critical severity
- 7.2 High severity
Spotted an error? Tell us.