FUXA: SQL injection in TDengine DAQ connector via backslash bypass of escapeTdString
cve-program · CVE-2026-47720
PublishedFUXA is a web-based Process Visualization (SCADA/HMI/Dashboard) software. Prior to 1.3.2, the TDengine DAQ storage connector's escapeTdString function in server/runtime/storage/tdengine/index.js doubles single quotes but does not escape backslashes. A remote unauthenticated attacker can submit a crafted sids tag identifier through GET /api/daq or the Socket.IO DAQ_QUERY event so TDengine interprets the backslash and quote sequence as SQL syntax. The injected query can return every row from fuxa.meters, exposing historical PLC tag values, device identifiers, and device names even when FUXA authentication is enabled. This issue is fixed in version 1.3.2.
Read the publisher's advisoryeuvd · EUVD-2026-61207
PublishedFUXA is a web-based Process Visualization (SCADA/HMI/Dashboard) software. Prior to 1.3.2, the TDengine DAQ storage connector's escapeTdString function in server/runtime/storage/tdengine/index.js doubles single quotes but does not escape backslashes. A remote unauthenticated attacker can submit a crafted sids tag identifier through GET /api/daq or the Socket.IO DAQ_QUERY event so TDengine interprets the backslash and quote sequence as SQL syntax. The injected query can return every row from fuxa.meters, exposing historical PLC tag values, device identifiers, and device names even when FUXA authentication is enabled. This issue is fixed in version 1.3.2.
Read the publisher's advisorynvd · CVE-2026-47720
PublishedFUXA is a web-based Process Visualization (SCADA/HMI/Dashboard) software. Prior to 1.3.2, the TDengine DAQ storage connector's escapeTdString function in server/runtime/storage/tdengine/index.js doubles single quotes but does not escape backslashes. A remote unauthenticated attacker can submit a crafted sids tag identifier through GET /api/daq or the Socket.IO DAQ_QUERY event so TDengine interprets the backslash and quote sequence as SQL syntax. The injected query can return every row from fuxa.meters, exposing historical PLC tag values, device identifiers, and device names even when FUXA authentication is enabled. This issue is fixed in version 1.3.2.
Read the publisher's advisoryosv · GHSA-h9fj-c2qr-76g2
Published## Summary The TDengine DAQ storage connector's `escapeTdString` at `server/runtime/storage/tdengine/index.js:10` doubles single quotes but does not escape backslashes. TDengine's SQL parser treats `\'` as a literal single quote inside a string, so a tag id of the form `x\' OR 1=1--` escapes the first single quote, lets the doubled quote close the string, and appends an injected clause that runs on the TDengine server. An attacker (Alice) sends the crafted `sids` value through `GET /api/daq` or the Socket.IO `DAQ_QUERY` event and reads every row in `fuxa.meters`, which holds the historical tag values of every PLC the FUXA instance records. ## Details The TDengine DAQ storage connector did not correctly sanitize user-controlled values before including them in SQL queries. A specially crafted tag identifier could bypass the intended escaping logic and alter the query executed against the TDengine database. This could allow unauthorized access to historical DAQ data stored in TDengine, including recorded tag values and related metadata. The issue has been fixed in version 1.3.2 by improving input escaping in the TDengine connector. ## Impact An attacker with network access to a FUXA instance configured with TDengine as the DAQ backend reads the entire historical tag-value archive: every PLC tag the instance has recorded, plus the associated device ids and device names. Turning on authentication does not close the gap: the Socket.IO `DAQ_QUERY` handler has no authorization check, and `/api/daq` accepts guest-level requests. No login is needed in the default configuration. **CVSS 3.1**: `AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N` (Medium, 5.3). CWE-89. --- A fix is available at https://github.com/frangoteam/FUXA/releases/tag/v1.3.2. --- *Found by [aisafe.io](https://aisafe.io)*
Read the publisher's advisoryAffected versions, risk and source history
Related advisories and sources
Publishers link these advisories through the identifiers shown below. A shared identifier or date alone does not tell you whether your software is affected or whether the advisories describe the same cause.
CVE-2026-47720 · CVE overview and exploitation status
cve-program · CVE-2026-47720
- https://github.com/frangoteam/FUXA/security/advisories/GHSA-h9fj-c2qr-76g2
- https://github.com/frangoteam/FUXA/pull/2343
- https://github.com/frangoteam/FUXA/commit/b78f6159d02a56ce5ff48207feb936afb3534fc8
- https://github.com/frangoteam/FUXA/releases/tag/v1.3.2
euvd · EUVD-2026-61207
- https://github.com/frangoteam/FUXA/security/advisories/GHSA-h9fj-c2qr-76g2
- https://github.com/frangoteam/FUXA/pull/2343
- https://github.com/frangoteam/FUXA/commit/b78f6159d02a56ce5ff48207feb936afb3534fc8
- https://github.com/frangoteam/FUXA/releases/tag/v1.3.2
nvd · CVE-2026-47720
- https://github.com/frangoteam/FUXA/commit/b78f6159d02a56ce5ff48207feb936afb3534fc8
- https://github.com/frangoteam/FUXA/pull/2343
- https://github.com/frangoteam/FUXA/releases/tag/v1.3.2
- https://github.com/frangoteam/FUXA/security/advisories/GHSA-h9fj-c2qr-76g2
osv · GHSA-h9fj-c2qr-76g2
Related changes
Linked by CVE identifierNo related changes are available here.