CVE-2026-47720 frangoteam CVE debrief

Who should care

Defenders responsible for FUXA deployments should assess exposure and prioritize upgrading to version 1.3.2 or later. They should also review compensating controls for exposed systems, monitor for suspicious activity, and track exceptions and retest remediated assets. Additionally, defenders should verify FUXA deployments for exposure, review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance, and plan

Why it matters

A vulnerability in FUXA's TDengine DAQ storage connector allows remote unauthenticated attackers to inject SQL queries, potentially exposing sensitive information. Defenders should prioritize verifying FUXA deployments for exposure and upgrading to version 1.3.2 or later.

• Potential exposure of historical PLC tag values
• Potential exposure of device identifiers
• Potential exposure of device names
• Verification of FUXA deployments for exposure

Technical summary

The TDengine DAQ storage connector's escapeTdString function in FUXA's server/runtime/storage/tdengine/index.js does not properly escape backslashes, allowing remote unauthenticated attackers to inject SQL queries. The vulnerability can be exploited through GET /api/daq or the Socket.IO DAQ_QUERY event, potentially exposing historical PLC tag values, device identifiers, and device names. The fix in version 1.3.2 addresses this issue by properly escaping backslashes and quotes, preventing SQL injection attacks. Defenders should prioritize verifying FUXA deployments for exposure and upgrading to version 1.3.2 or later.

Defensive priority

Defenders should prioritize verifying FUXA deployments for exposure and upgrading to version 1.3.2 or later.

Recommended defensive actions

• Verify FUXA deployments for exposure
• Upgrade to version 1.3.2 or later
• Monitor for suspicious activity
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, its impact, and the fix in version 1.3.2. The vulnerability allows remote unauthenticated attackers to inject SQL queries, potentially exposing historical PLC tag values, device identifiers, and device names. The TDengine DAQ storage connector's escapeTdString function in server/runtime/storage/tdengine/index.js does not properly escape backslashes, leading to potential SQL injection attacks. The fix in version 1.3.2 addresses this issue by properly escaping backslash,

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.