Quick answers
- Is CVE-2025-69970 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-69970 being exploited in the wild.
- How severe is CVE-2025-69970?
- Medium severity, with a CVSS score of 4, published 3 February 2026.
- Which products and versions are affected?
- fuxa-server (npm) SEMVER:introduced=0,last_affected=1.2.7.
- Is there a fix for CVE-2025-69970?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2025-69970 attacked?
- It is attacked over the network.
- Am I affected by CVE-2025-69970?
- Check whether you run fuxa-server (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability exists in server/settings.default.js, where the 'secureEnabled' flag is commented out, causing the application to initialize with authentication disabled (CWE-1188: insecure default, CWE-306: missing authentication). The root cause is improper default configuration that leaves a security-critical flag disabled. An unauthenticated attacker on the network can access the application immediately after installation without any preconditions, gaining the ability to call sensitive API endpoints, modify projects, and control connected industrial equipment. The vulnerable versions extend from 0 through at least 1.2.7. Patch or configuration fix availability is not specified in the advisory.
Affected products
- FUXA FUXA up to and including 1.2.7
Identifiers
- CVE-2025-69970
- GHSA-r5m2-fqcf-qrf7
Timeline
- 2026-02-03: disclosed
- 2026-02-04: advisory: GitHub advisory GHSA-r5m2-fqcf-qrf7 published