CVE-2025-69970 — Frangoteam FUXA 1.2.7 Missing Authentication via Insecure Default Configuration

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

1. Identify exposed assets running the affected vendor/product/version combinations (Frangoteam Fuxa).
2. The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
3. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
4. Exploitation requires user interaction: tighten email/web filtering and warn affected users.
5. Search available logs for exploit probes matching the vulnerability class (access control), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-1188 · Insecure Default Initialization of Resource

Other CVEs with this weakness →

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.52%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

• Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
• Audit administrative actions and access to resources outside each user’s normal pattern.

Analysis and videos

CVE-2025-69970: Frangoteam FUXA 1.2.7 Missing Authentication via Insecure Default Configuration
FUXA 1.2.7 initializes with authentication disabled because the 'secureEnabled' flag is commented out by default in server/settings.default.js. According to the CNA record, unauthenticated remote attackers could reach sensitive API endpoints, modify projects and control industrial equipment. The CNA assigned a CVSS 3.1 base score of 9.3 (critical), and no fixed version is listed in the sources consulted.

Timeline

What happened to this CVE, newest first.

• 2026
• SSVC assessment updated
  Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
• Record published
  Oct 13, 2026
• CVSS changed · 9.3
  Oct 13, 2026 · NIST National Vulnerability Database
• Source status changed · → Analyzed
  Oct 13, 2026 · NIST National Vulnerability Database
• Record created in this database
  Oct 13, 2026 · NIST National Vulnerability Database
• CVE published
  Feb 3, 2026 · mitre

Source activity

Repeated readings are counted rather than listed.

• 1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

1 on the record

• github.com/frangoteam/FUXA/blob/master/server/settings.default.js
  Product, NIST National Vulnerability Database

Elsewhere on this site

Related CVEs (same products)

• Critical CVE-2025-69985 Authentication Bypass Using an Alternate Path or Channel in Frangoteam Fuxa Feb 24, 2026
• Critical CVE-2026-25938 FUXA Unauthenticated Remote Code Execution in Node-RED Integration Feb 9, 2026
• Critical CVE-2026-25939 FUXA Unauthenticated Remote Arbitrary Scheduler Write Feb 9, 2026
• High CVE-2026-25951 FUXA has a Path Traversal Sanitization Bypass Feb 9, 2026
• Critical CVE-2026-25893 FUXA Unauthenticated Remote Code Execution via Admin JWT Minting Feb 9, 2026
• Critical CVE-2026-25894 FUXA Unauthenticated Remote Code Execution via Hardcoded JWT Secret in Default Configuration Feb 9, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

• No fixed version, patch or mitigation documented.
• No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
• No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
• No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2025-69970 is "Frangoteam FUXA 1.2.7 Missing Authentication via Insecure Default Configuration", rated Critical. It affects Fuxa (Frangoteam); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 9.3 describes technical severity. EPSS 0.52% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.