Cyber Resilience

CVE-2025-69970

Critical

Published: 03 February 2026

Published
03 February 2026
Modified
10 February 2026
KEV Added
Patch
CVSS Score v3.1 9.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N
EPSS Score 0.0046 36.6th percentile
Risk Priority 70 floored blend · peak EPSS

Summary

CVE-2025-69970 is a critical-severity Initialization of a Resource with an Insecure Default (CWE-1188) vulnerability in Frangoteam Fuxa. Its CVSS base score is 9.3 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 36.6th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified are NIST 800-53 AC-14 (Permitted Actions Without Identification or Authentication) and AC-3 (Access Enforcement).

Deeper analysis

CVE-2025-69970 is an insecure default configuration vulnerability in FUXA version 1.2.7, published on 2026-02-03. The flaw originates in the server/settings.default.js file, where the 'secureEnabled' flag is commented out by default. This causes the application to initialize with authentication disabled, exposing sensitive functionality without any protective measures.

Unauthenticated remote attackers can exploit this vulnerability over the network with low attack complexity and no required privileges, though some user interaction is needed. Exploitation allows immediate access to sensitive API endpoints post-installation, enabling attackers to modify projects and control connected industrial equipment. The issue carries a CVSS v3.1 base score of 9.3 (AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N) and maps to CWE-1188.

The vulnerable default configuration is directly observable in the settings.default.js file on the project's GitHub repository at https://github.com/frangoteam/FUXA/blob/master/server/settings.default.js.

EU & UK References

Vulnerability details

FUXA v1.2.7 contains an insecure default configuration vulnerability in server/settings.default.js. The 'secureEnabled' flag is commented out by default, causing the application to initialize with authentication disabled. This allows unauthenticated remote attackers to access sensitive API endpoints, modify projects, and control…

more

industrial equipment immediately after installation.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise TechniquesAI

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
Why these techniques?

Default-disabled authentication in a public-facing industrial web app directly enables unauthenticated remote exploitation and access to sensitive functionality.

Confidence: HIGH · MITRE ATT&CK Enterprise v19.0

CVEs Like This One

CVE-2026-25894Same product: Frangoteam Fuxa
CVE-2025-69983Same product: Frangoteam Fuxa
CVE-2026-25938Same product: Frangoteam Fuxa
CVE-2026-25939Same product: Frangoteam Fuxa
CVE-2026-25893Same product: Frangoteam Fuxa
CVE-2025-69971Same product: Frangoteam Fuxa
CVE-2026-25895Same product: Frangoteam Fuxa
CVE-2026-25751Same product: Frangoteam Fuxa
CVE-2025-69985Same product: Frangoteam Fuxa
CVE-2025-69981Same product: Frangoteam Fuxa

Affected Assets

frangoteam
fuxa
1.2.7

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

prevent

CM-6 requires establishing and implementing secure configuration settings, directly mitigating the insecure default in server/settings.default.js that disables authentication.

prevent

AC-3 enforces approved authorizations for access to system resources, preventing unauthenticated attackers from reaching sensitive API endpoints.

prevent

AC-14 explicitly authorizes and limits permitted actions without identification or authentication, restricting modifications to projects and control of industrial equipment.

References