CVE-2026-47720

MEDIUMPre-NVD 5.35.3—
EchelonGraph scoreLOW confidence

Score 5.3 from GitHub Security Advisory published 2026-06-08. the CNA's CVSS baseline 5.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:github_m, epss, ghsa
5.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.3Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

FUXA has SQL Injection in its TDengine DAQ connector via backslash bypass of escapeTdString

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*

CVSS v3
5.3
EG Score
5.3(low)
EG Risk
—
EPSS
24.2%
KEV
Not listed

Published

June 8, 2026

Last Modified

June 8, 2026

Vendor Advisories for CVE-2026-47720(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
npmfuxa-server—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
fuxa-server———

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 0× in last 7d / 19× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-15 20:31 UTCGHSA enrichment
  2. 2026-07-14 02:42 UTCGHSA enrichment
  3. 2026-07-11 21:49 UTCGHSA enrichment
  4. 2026-07-10 21:24 UTCGHSA enrichment
  5. 2026-07-09 03:58 UTCGHSA enrichment
  6. 2026-07-08 02:37 UTCGHSA enrichment
  7. 2026-07-05 22:16 UTCGHSA enrichment
  8. 2026-07-04 21:50 UTCGHSA enrichment
  9. 2026-07-03 20:59 UTCGHSA enrichment
  10. 2026-07-02 20:30 UTCGHSA enrichment
  11. 2026-07-01 20:05 UTCGHSA enrichment
  12. 2026-06-30 19:40 UTCGHSA enrichment
  13. 2026-06-29 19:15 UTCGHSA enrichment
  14. 2026-06-28 17:57 UTCGHSA enrichment
  15. 2026-06-27 17:31 UTCGHSA enrichment
  16. 2026-06-26 17:05 UTCGHSA enrichment
  17. 2026-06-25 16:41 UTCGHSA enrichment
  18. 2026-06-24 16:16 UTCGHSA enrichment
  19. 2026-06-23 15:51 UTCGHSA enrichment
  20. 2026-06-22 13:47 UTCGHSA enrichment
  21. 2026-06-21 10:54 UTCGHSA enrichment
  22. 2026-06-20 07:53 UTCGHSA enrichment
  23. 2026-06-19 03:28 UTCGHSA enrichment
  24. 2026-06-18 02:51 UTCGHSA enrichment
  25. 2026-06-17 02:26 UTCGHSA enrichment
Show 12 more
  1. 2026-06-16 02:01 UTCGHSA enrichment
  2. 2026-06-15 01:36 UTCGHSA enrichment
  3. 2026-06-14 23:18 UTCEPSS rescore
  4. 2026-06-14 01:11 UTCGHSA enrichment
  5. 2026-06-13 23:00 UTCEPSS rescore
  6. 2026-06-13 00:46 UTCGHSA enrichment
  7. 2026-06-12 23:12 UTCEPSS rescore
  8. 2026-06-12 00:22 UTCGHSA enrichment
  9. 2026-06-10 23:57 UTCGHSA enrichment
  10. 2026-06-09 23:32 UTCGHSA enrichment
  11. 2026-06-08 23:08 UTCEG score recompute
  12. 2026-06-08 23:08 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-47720?
CVE-2026-47720 is a medium vulnerability published on June 8, 2026. FUXA has SQL Injection in its TDengine DAQ connector via backslash bypass of escapeTdString 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…
When was CVE-2026-47720 disclosed?
CVE-2026-47720 was first published in the National Vulnerability Database on June 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-47720 actively exploited?
CVE-2026-47720 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 24.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-47720?
CVE-2026-47720 has a CVSS v4.0 base score of 5.3 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-47720?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-47720, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-47720

Explore →

Is Your Infrastructure Affected by CVE-2026-47720?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs