Is CVE-2026-43947 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-43947 being exploited in the wild.

How severe is CVE-2026-43947?

High severity, with a CVSS score of 4, published 21 July 2026.

Which products and versions are affected?

Frangoteam FUXA 1.3.0; fuxa-server (npm) = 1.3.0, SEMVER:introduced=1.3.0,fixed=1.3.1.

Is there a fix for CVE-2026-43947?

Yes. fuxa-server (npm): upgrade to 1.3.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-43947 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-43947?

Check whether you run Frangoteam FUXA or fuxa-server (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-43947: frangoteam FUXA unauthenticated RCE in /api/runscript

CVE-2026-43947 · Severity: high · CVSS 4 · Published 2026-07-21

FUXA is a web-based industrial control and dashboard platform used to visualize and manage industrial processes. A security flaw allows an unauthenticated attacker to bypass security checks and execute arbitrary commands on the server. This could lead to a total takeover of the system, unauthorized access to industrial equipment, and theft of sensitive operational data.

Technologies: Frangoteam FUXA, fuxa-server (npm). Vendors: Frangoteam, npm.

Quick answers

Is CVE-2026-43947 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-43947 being exploited in the wild.
How severe is CVE-2026-43947?: High severity, with a CVSS score of 4, published 21 July 2026.
Which products and versions are affected?: Frangoteam FUXA 1.3.0; fuxa-server (npm) = 1.3.0, SEMVER:introduced=1.3.0,fixed=1.3.1.
Is there a fix for CVE-2026-43947?: Yes. fuxa-server (npm): upgrade to 1.3.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-43947 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-43947?: Check whether you run Frangoteam FUXA or fuxa-server (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

fuxa-server (npm): upgrade to 1.3.1 or later
```
npm install fuxa-server@1.3.1
```

Technical details

An unauthenticated remote code execution (RCE) vulnerability exists in FUXA version 1.3.0 due to an authorization bypass in the script execution engine. The `POST /api/runscript` endpoint validates permissions against a stored script's ID; however, if the `test: true` flag is included in the request, the server executes attacker-supplied code instead of the stored script. Because the middleware automatically assigns a guest token to unauthenticated requests and scripts without explicit permissions default to being accessible, an attacker can leverage a known script ID (obtainable via information disclosure) to execute arbitrary Node.js code. The vulnerability allows full access to the underlying operating system via the `child_process` module. This issue is resolved in version 1.3.1.

Affected products

frangoteam FUXA 1.3.0

Identifiers

CVE-2026-43947
GHSA-rg3m-cfq7-g6h6

Timeline

2026-03-19: patched: Fix merged into master branch
2026-04-09: other: Version 1.3.1 released
2026-05-19: advisory: GitHub Security Advisory published
2026-07-21: disclosed: CVE published to NVD

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.