Is CVE-2025-69971 exploited in the wild?

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

How severe is CVE-2025-69971?

High severity, with a CVSS score of 8.1, published 7 March 2026.

Which products and versions are affected?

Frangoteam FUXA <= 1.2.11, 1.2.7; @frangoteam/fuxa (npm) <= 1.2.11, SEMVER:introduced=0,fixed=1.3.0; fuxa-server (npm) SEMVER:introduced=0,last_affected=1.2.7.

Is there a fix for CVE-2025-69971?

Yes. @frangoteam/fuxa (npm): upgrade to 1.3.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2025-69971 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2025-69971?

Check whether you run Frangoteam FUXA, @frangoteam/fuxa (npm) 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-2025-69971: frangoteam FUXA hardcoded JWT signing secret fallback

Q: Which products and versions are affected?

Frangoteam FUXA <= 1.2.11, 1.2.7; @frangoteam/fuxa (npm) <= 1.2.11, SEMVER:introduced=0,fixed=1.3.0; fuxa-server (npm) SEMVER:introduced=0,last_affected=1.2.7.

Q: Is there a fix for CVE-2025-69971?

Yes. @frangoteam/fuxa (npm): upgrade to 1.3.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2025-69971 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2025-69971?

Check whether you run Frangoteam FUXA, @frangoteam/fuxa (npm) 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-2025-69971 · Severity: high · CVSS 8.1 · Published 2026-03-07

FUXA, an open-source industrial web-based SCADA/HMI platform, contains a security flaw where it uses a publicly known, hardcoded password to sign digital login tokens. If an administrator has not manually configured a custom security key, an attacker can use this known password to create their own valid login tokens. This allows an unauthorized user to bypass authentication entirely and gain full access to the system and its industrial controls.

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

Quick answers

Is CVE-2025-69971 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2025-69971 being exploited in the wild.
How severe is CVE-2025-69971?: High severity, with a CVSS score of 8.1, published 7 March 2026.
Which products and versions are affected?: Frangoteam FUXA <= 1.2.11, 1.2.7; @frangoteam/fuxa (npm) <= 1.2.11, SEMVER:introduced=0,fixed=1.3.0; fuxa-server (npm) SEMVER:introduced=0,last_affected=1.2.7.
Is there a fix for CVE-2025-69971?: Yes. @frangoteam/fuxa (npm): upgrade to 1.3.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2025-69971 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2025-69971?: Check whether you run Frangoteam FUXA, @frangoteam/fuxa (npm) 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

@frangoteam/fuxa (npm): upgrade to 1.3.0 or later
```
npm install @frangoteam/fuxa@1.3.0
```

Technical details

FUXA (up to version 1.2.11) utilizes a hardcoded fallback JWT signing secret ('frangoteam751') within its `jwt-helper.js` component. When the `secretCode` configuration is left empty, the application defaults to this static string to sign JSON Web Tokens. A remote, unauthenticated attacker can exploit this by manually crafting and signing a JWT using the known secret, granting them unauthorized administrative access to the web interface. The vulnerability is classified as CWE-321 (Use of Hard-coded Cryptographic Key) and has been remediated in version 1.3.0 by implementing secure random secret generation when no custom code is provided.

Affected products

frangoteam FUXA <= 1.2.11

Identifiers

CVE-2025-69971
GHSA-2r8f-cf6w-x5vq
GHSA-c8m8-3jcr-6rj5

Timeline

2026-03-07: advisory: GitHub Advisory GHSA-c8m8-3jcr-6rj5 published
2026-03-07: patched: Issue addressed in version 1.3.0

References

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