Is CVE-2026-47717 exploited in the wild?

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

How severe is CVE-2026-47717?

High severity, with a CVSS score of 7.5, published 12 August 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-47717?

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-47717 attacked?

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

Am I affected by CVE-2026-47717?

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-47717: FUXA unauthenticated project data disclosure in API

CVE-2026-47717 · Severity: high · CVSS 7.5 · Published 2026-08-12

FUXA, an open-source industrial monitoring and control (HMI/SCADA) platform, contains a security flaw that allows unauthorized users to download entire project configurations. This includes sensitive information such as server-side automation scripts, device connection details, and alarm settings. An attacker could use this data to understand internal operations or plan more disruptive attacks against industrial infrastructure.

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

Quick answers

Is CVE-2026-47717 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-47717 being exploited in the wild.
How severe is CVE-2026-47717?: High severity, with a CVSS score of 7.5, published 12 August 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-47717?: 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-47717 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-47717?: 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

The `/api/project` endpoint in FUXA v1.3.0 fails to enforce proper authentication due to a flaw in the `verifyToken` middleware. When no authentication token is provided, the system automatically generates and signs a valid 'guest' JWT, which passes the security check. While some UI elements are filtered, the backend response still includes sensitive metadata such as full server-side script source code, device communication endpoints, HMI SVG layouts, and alarm thresholds. This is classified as an insertion of sensitive information into sent data (CWE-201). The vulnerability is addressed in version 1.3.1.

Affected products

frangoteam FUXA 1.3.0

Identifiers

CVE-2026-47717
GHSA-q3w6-q3hc-c5x6

Timeline

2026-05-26: disclosed
2026-05-27: advisory
2026-05-27: patched: Fixed in version 1.3.1

References

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