CVE-2025-69970
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
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| frangoteam | fuxa | 1.2.7 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| 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. |
| 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. |
Attack-Flow Graph
AI Powered Q&A
How can this vulnerability be detected on my network or system? Can you suggest some commands?
[{'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]
What immediate steps should I take to mitigate this vulnerability?
[{'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]
Can you explain this vulnerability to me?
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.
How can this vulnerability impact me? :
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.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know