CVE-2025-69970
Unknown Unknown - Not Provided
Insecure Default Config in FUXA v1.2.7 Enables Unauthorized Access

Publication date: 2026-02-03

Last updated on: 2026-02-10

Assigner: MITRE

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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-02-03
Last Modified
2026-02-10
Generated
2026-06-16
AI Q&A
2026-02-03
EPSS Evaluated
2026-06-14
NVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
frangoteam fuxa 1.2.7
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-79 The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.
CWE-1188 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.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Detection Guidance

[{'type': 'paragraph', 'content': "This vulnerability can be detected by checking if the 'secureEnabled' flag in the FUXA server configuration file (server/settings.default.js) is commented out or disabled, which causes authentication to be turned off."}, {'type': 'paragraph', 'content': "To detect this on your system, you can inspect the configuration file directly. For example, use the following command to check if 'secureEnabled' is commented out:"}, {'type': 'list_item', 'content': "grep '^\\s*//\\s*secureEnabled' path/to/server/settings.default.js"}, {'type': 'paragraph', 'content': 'Alternatively, you can check if the FUXA server is allowing unauthenticated access by attempting to access sensitive API endpoints without credentials.'}, {'type': 'list_item', 'content': 'curl -i http://<fuxa-server-ip>:<port>/api/projects'}, {'type': 'paragraph', 'content': 'If the response returns data without requiring authentication, the vulnerability is present.'}] [1]

Mitigation Strategies

[{'type': 'paragraph', 'content': "To mitigate this vulnerability immediately, you should enable authentication by uncommenting and setting the 'secureEnabled' flag to true in the server/settings.default.js configuration file."}, {'type': 'list_item', 'content': "Edit server/settings.default.js and change the line from '// secureEnabled: false' (or commented out) to 'secureEnabled: true'."}, {'type': 'paragraph', 'content': 'After making this change, restart the FUXA server to apply the new configuration.'}, {'type': 'paragraph', 'content': 'Additionally, restrict network access to the FUXA server to trusted hosts only until authentication is properly enabled.'}] [1]

Executive Summary

The vulnerability in FUXA v1.2.7 is due to an insecure default configuration in the server/settings.default.js file. Specifically, the 'secureEnabled' flag is commented out by default, which causes the application to start with authentication disabled.

As a result, unauthenticated remote attackers can access sensitive API endpoints without any restriction immediately after installation.

This allows attackers to modify projects and control industrial equipment through the application.

Impact Analysis

This vulnerability can have serious impacts because it allows unauthenticated remote attackers to gain unauthorized access to sensitive API endpoints.

  • Attackers can modify projects within the application.
  • Attackers can control industrial equipment connected through the application.

Such unauthorized access and control can lead to operational disruptions, data manipulation, and potential safety hazards in industrial environments.

Compliance Impact

I don't know

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2025-69970. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart