CVE-2026-43945: frangoteam FUXA authentication bypass and RCE via path manipulation

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

FUXA is a web-based software used for industrial process visualization and control (SCADA/HMI). A security flaw allows an unauthenticated attacker to bypass security controls and execute commands on the server with root privileges. This could lead to the theft of industrial data, manipulation of PLC tags, or a complete shutdown of industrial operations.

Technologies: Frangoteam FUXA, @frangoteam/fuxa (npm). Vendors: Frangoteam, npm.

Quick answers

Is CVE-2026-43945 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-43945 being exploited in the wild.
How severe is CVE-2026-43945?
High severity, with a CVSS score of 4, published 21 July 2026.
Which products and versions are affected?
Frangoteam FUXA >= 1.2.11, < 1.3.1, 1.2.11 to 1.3.0; @frangoteam/fuxa (npm) >= 1.2.11, < 1.3.1, SEMVER:introduced=1.2.11,fixed=1.3.1.
Is there a fix for CVE-2026-43945?
Yes. @frangoteam/fuxa (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-43945 attacked?
It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-43945?
Check whether you run Frangoteam FUXA or @frangoteam/fuxa (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

  • @frangoteam/fuxa (npm): upgrade to 1.3.1 or later
    npm install @frangoteam/fuxa@1.3.1

Technical details

A path confusion vulnerability exists in the authentication middleware of FUXA. The server uses a substring match on the full URL (including query parameters) via 'req.originalUrl' to exclude certain paths like '/socket.io' from authentication. An attacker can bypass security checks by appending a crafted query string (e.g., '?x=/socket.io') to administrative requests, tricking the middleware into treating the request as a public WebSocket handshake. This bypasses 'secureEnabled' and 'nodeRedAuthMode' checks, allowing access to privileged Node-RED endpoints where code execution can be achieved. The issue is fixed in version 1.3.1 by switching to 'req.path' for routing decisions.

Affected products

  • frangoteam FUXA 1.2.11 to 1.3.0

Identifiers

  • CVE-2026-43945
  • GHSA-p69w-mmfv-xrfj

Timeline

  • 2026-04-09: patched: 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.