Is CVE-2026-47718 exploited in the wild?

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

How severe is CVE-2026-47718?

Medium severity, with a CVSS score of 4, published 12 August 2026.

Which products and versions are affected?

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

Is there a fix for CVE-2026-47718?

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

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

Am I affected by CVE-2026-47718?

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-47718: frangoteam FUXA authentication bypass in protected read APIs

CVE-2026-47718 · Severity: medium · CVSS 4 · Published 2026-08-12

FUXA, an open-source web-based SCADA/HMI system, contains a security flaw where its 'secure mode' fails to properly restrict access. Unauthorized users or those with invalid credentials can still view sensitive project data, system alarms, and scheduled tasks. This could allow an attacker to perform reconnaissance on industrial control systems or access proprietary project configurations.

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

Quick answers

Is CVE-2026-47718 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-47718 being exploited in the wild.
How severe is CVE-2026-47718?: Medium severity, with a CVSS score of 4, published 12 August 2026.
Which products and versions are affected?: Frangoteam FUXA 1.3.0-2773; fuxa-server (npm) = 1.3.0-2773, SEMVER:introduced=1.3.0-2773,fixed=1.3.1.
Is there a fix for CVE-2026-47718?: 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-47718 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-47718?: 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 authentication bypass exists in FUXA version 1.3.0-2773 due to improper token validation in 'server/api/jwt-helper.js'. The 'verifyToken()' function incorrectly treats missing or invalid JSON Web Tokens (JWT) as a 'guest' context rather than rejecting the request. When 'secureEnabled=true' is configured, API endpoints for projects, alarms, and the scheduler fail to verify if the guest context should be permitted, resulting in the disclosure of sensitive metadata to unauthenticated network attackers. This has been patched in version 1.3.1.

Affected products

frangoteam FUXA 1.3.0-2773

Identifiers

CVE-2026-47718
GHSA-r9g5-7q8j-958c

Timeline

2026-05-26: patched: Version 1.3.1 released
2026-05-28: advisory: GitHub Advisory published

References

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