# CVE-2026-47720: FUXA: SQL injection in TDengine DAQ connector via backslash bypass of escapeTdString

> Remote unauthenticated attackers can inject SQL via crafted tag identifiers to expose historical PLC data and device information in FUXA.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Aug 2026
- **Updated:** 19 Aug 2026
- **Also known as:** GHSA-h9fj-c2qr-76g2

## What is CVE-2026-47720?

CVE-2026-47720 is a medium-severity SQL injection vulnerability in frangoteam FUXA, published on 18 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

FUXA 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.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2026-47720?

2 open source packages ship an affected version, including fuxa-server.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `fuxa-server` | npm | All versions to 1.1.14-1243 | None |
| `fuxa-server` | npm | All versions to 1.1.14-1243 | None |

## How do I fix CVE-2026-47720?

No fix has been published for CVE-2026-47720 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-47720 being exploited?

There is no known exploitation of CVE-2026-47720 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-47720 and fix it if it is affected.

What it is: CVE-2026-47720 is a medium-severity SQL injection vulnerability in frangoteam FUXA, published on 18 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-47720 in the wild and no public exploit code.

Affected packages and fixed versions:
- fuxa-server (npm): affected all versions up to 1.1.14-1243; no fix listed
- fuxa-server (npm): affected all versions up to 1.1.14-1243; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-47720/ (Markdown: https://insights.sbomify.com/CVE-2026-47720/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-47720
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-47720
- OSV: https://osv.dev/vulnerability/CVE-2026-47720

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-47720/
Summaries are generated and may contain mistakes; the official description above is the record.