/

CVE-2025-69970

Severity:

CRITICAL RISK

(9.3)

Insecure Default Configuration in FUXA

CVE-2025-69970

Undergoing Analysis

Vulnerability type

Category:

Insecure Default Configuration

CWE:

CWE-79

Impact:

Unauthenticated Remote Access and Control of Industrial Systems

Severity:

CRITICAL RISK

(9.3)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

FUXA v1.2.7 ships with an insecure default configuration where the secureEnabled flag is commented out, causing the server to start with authentication disabled.

In this state, unauthenticated remote users can immediately access sensitive API endpoints, modify projects, and issue commands to control industrial equipment right after installation.

Affected context

This vulnerability appears in fresh or reset FUXA v1.2.7 deployments that rely on the default server/settings.default.js configuration.

When administrators do not explicitly enable and configure authentication before exposing the system, the server runs with open access to APIs used for project management and industrial device control.

Environments where the application is reachable from corporate networks or the internet are particularly exposed, especially in OT or industrial control contexts.

Exploit preconditions

  • Attack surface: Network-accessible FUXA server HTTP(S) interface
  • Required access: None; attacker can be fully unauthenticated
  • Trigger point: Initial server startup with default settings.default.js where secureEnabled remains commented out
  • Why exploitation is possible: The application is designed to allow privileged operations through the API layer, but the default configuration disables authentication, leaving these endpoints unprotected until a human explicitly changes the settings

Why this happens

The root cause is an insecure-by-default configuration decision around authentication.

The secureEnabled flag, responsible for protecting API endpoints with authentication, is commented out in the shipped server/settings.default.js file.

As a result, unless operators proactively enable security before deployment, the application initializes in an effectively "open" mode.

This is a classic configuration-hardening failure, where powerful administrative capabilities are exposed without requiring identity verification or session management.

Potential impact

  • Unauthenticated modification of industrial visualization and control projects
  • Unauthorized issuing of commands to connected industrial equipment
  • Disruption or manipulation of industrial processes and automation logic
  • Loss of integrity and availability of operational technology (OT) systems
  • Potential pivot into adjacent OT/IT network segments through compromised control interfaces

General mitigation guidance

Mitigation should center on enforcing secure defaults and tightening trust boundaries around authentication and authorization.

Common defensive patterns include:

  • Reversing the default: ensure authentication is enabled by default and requires explicit action to disable, if disabling is allowed at all
  • Validating configuration at startup and refusing to run when security-critical options (like authentication) are disabled in production-like environments
  • Separating runtime configuration from sample/example configuration files to avoid deploying development defaults into production
  • Applying least privilege to API endpoints so that only authenticated and appropriately authorized roles can modify projects or control equipment
  • Restricting network exposure of the FUXA server, especially from untrusted networks, and placing it behind secure gateways or VPNs

How teams detect issues like this

Detection can combine configuration review, network monitoring, and code-level checks:

  • Static analysis or configuration linting to flag builds where secureEnabled is commented out or set to a non-secure state
  • CI/CD policy checks that reject deployments when core authentication flags are missing or disabled
  • Code review practices that treat authentication toggles and default configuration files as high-risk areas requiring security sign-off
  • Runtime monitoring and logging for anomalous unauthenticated access to administrative or control endpoints
  • Periodic security posture scans that simulate unauthenticated requests to critical APIs to verify that authentication is enforced

Sources

SourceLink
github.comgithub.com/frangoteam/FUXA/blob/master/server/settings.default.js

Frequently asked

questions

Yes. If the FUXA server is reachable over the network and still using the insecure default configuration, an attacker can interact with critical API endpoints without any authentication.

None beyond basic network connectivity to the FUXA server.

No user account, session cookie, or prior foothold is required when authentication is disabled by default.

Ensure that authentication is enabled by default and enforced on all sensitive endpoints.

Treat any configuration where authentication is off as an invalid state for production and make the application fail closed when such a configuration is detected.

Adopt secure-by-default configuration practices, implement automated checks that block insecure settings in CI/CD, and restrict external network access until authentication and authorization are fully configured and validated.

Find out what's already
exploitable in your codebase.