FUXA contains an insecure default configuration vulnerability

published 2026-02-03 9 mo ago modified 2026-06-17 4 mo ago also GHSA-r5m2-fqcf-qrf7 , EUVD-2025-206711

cvss: 9.3; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.5%; EPSS 0.5% chance of exploitation in 30 days, percentile 44%
public exploits: 0; none known

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 industrial equipment immediately after installation.

CISA SSVC

Exploitation: none
Automatable: yes
Technical impact: total
Assessed: 9 mo ago (2026-02-05)

Exploit prediction

0.52% chance of exploitation in the next 30 days, higher than 44% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
CISA ADP	3.1	9.3	CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N
CNA	3.1	9.3	CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N

Affected packages

ecosystem	package	affected	fixed in
npm	fuxa-server	<=1.2.7	no fix listed

Classification

Weakness

CWE-1188 Initialization of a Resource with an Insecure Default
CWE-306 Missing Authentication for Critical Functionality

References

github.com /frangoteam/FUXA/blob/master/server/settings.default.js
web, product
nvd.nist.gov /vuln/detail/CVE-2025-69970
advisory
github.com /frangoteam/FUXA/blob
package

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary