VulnerabilityPublished 3 Feb 2026Updated 9 Feb 2026

CVE-2025-69970: FUXA v1.2.7 contains an insecure default configuration

Affects FUXASource CVE Database V5

Not known to be exploited · CVSS 9.3 Critical.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

9.3Critical

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.5% chance of exploitation in 30 days – higher than 44% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Changed
Confidentiality: High
Integrity: High
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 3 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
GitHubfrangoteam/FUXA`pkg:github/frangoteam/FUXA`Other threats	Affected =1.2.7	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Immediately review all FUXA installations to verify whether the 'secureEnabled' flag is enabled in the server/settings.default.js or equivalent configuration files.
Manually enable the 'secureEnabled' flag to enforce authentication before deploying or using the application in production environments.
Conduct a comprehensive audit of existing FUXA deployments to identify any unauthorized access or modifications that may have occurred due to this vulnerability.
Implement network segmentation and access controls to limit exposure of FUXA servers to untrusted networks, reducing the attack surface.
Monitor API access logs for unusual or unauthorized activity, especially immediately after installation or configuration changes.
Educate system administrators and deployment teams about the importance of secure default configurations and verify security settings as part of deployment checklists.
Engage with FUXA vendors or community to track patch releases or official security advisories and apply updates promptly once available.
Consider deploying additional authentication or identity management layers in front of FUXA to add defense-in-depth.

Description

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.

Impact

For European organizations, especially those in manufacturing, energy, and critical infrastructure sectors relying on FUXA for industrial control or project management, this vulnerability poses a severe risk. Unauthorized access to sensitive API endpoints can lead to data breaches, manipulation of project data, and unauthorized control over industrial equipment, potentially causing operational disruptions, safety hazards, and financial losses. The confidentiality and integrity of industrial control systems are at high risk, which could also lead to regulatory non-compliance under GDPR and NIS Directive frameworks. The availability impact is rated low, but the potential for cascading effects in industrial environments could indirectly affect availability. The vulnerability's ease of exploitation without authentication increases the likelihood of attacks, especially in environments where default configurations are not audited or changed post-installation. This threat could also undermine trust in automation and industrial IoT deployments across Europe.

CWE-1188Initialization of a Resource with an Insecure Default (opens in a new tab)
Base weakness
The product initializes or sets a resource with a default that is intended to be changed by the product's installer, administrator, or maintainer, but the default is not secure.
OWASP Cheat Sheets
Forgot Password (opens in a new tab)
OWASP ASVS 4.0.3
V2.3.1 (opens in a new tab)
V2.6.2 (opens in a new tab)
V2.7.6 (opens in a new tab)
Attack patterns
Exploitation of Thunderbolt Protection Flaws (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

github.com/frangoteam/FUXA/blob/master/server/settings.default.js (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 11 Feb 2026, 11:17 UTC

WeaknessesCWE-1188

Technical details

References

Community reviews

Related threats