CVE-2026-47720Network attack vector

Historical data disclosure via backslash SQL injection

Published Aug 18, 2026 · Updated Aug 19, 2026

SQL injection in the TDengine DAQ connector in Frangoteam FUXA before 1.3.2 allows remote attackers to read stored DAQ data. In server/runtime/storage/tdengine/index.js, escapeTdString doubles single quotes but leaves backslashes intact before tag identifiers are interpolated into SQL, so a backslash-quote sequence can terminate the string and append attacker-controlled clauses. When FUXA uses TDengine as its DAQ backend, GET /api/daq and the Socket.IO DAQ_QUERY event are reachable without login and expose historical PLC tag values, device identifiers, and device names even when authentication is enabled.

CVSS severity5.3
Medium
EPSS probability0.49%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

SQL injection in the TDengine DAQ connector in Frangoteam FUXA before 1.3.2 allows remote attackers to read stored DAQ data. In server/runtime/storage/tdengine/index.js, escapeTdString doubles single quotes but leaves backslashes intact before tag identifiers are interpolated into SQL, so a backslash-quote sequence can terminate the string and append attacker-controlled clauses. When FUXA uses TDengine as its DAQ backend, GET /api/daq and the Socket.IO DAQ_QUERY event are reachable without login and expose historical PLC tag values, device identifiers, and device names even when authentication is enabled.

The record

CVE
CVE-2026-47720
Published
Aug 18, 2026
Updated
Aug 19, 2026
Vendor
Frangoteam
Product
FUXA
Classifications
CWE-89, T1190
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Aug 18, 2026CVE publishedPublication date reported by the CVE source.
  2. Aug 19, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=< 1.3.2

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

Frangoteam · FUXAversion=< 1.3.2

Published CVSS scores

5.3GitHub Advisory DatabaseCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-89Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
T1190Exploit Public-Facing Application

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo