CVE-2026-72586
Received Received - Intake

Authentication Bypass in FUXA Allows Data Access

Vulnerability report for CVE-2026-72586, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-08-10

Last updated on: 2026-08-10

Assigner: 309f9ea4-e3e9-4c6c-b79d-e8eb01244f2c

Description

A missing authentication vulnerability in frangoteam/FUXA through 1.3.3 allows an unauthenticated remote attacker to query all historical sensor data via the DAQ_QUERY Socket.IO event. When secureEnabled=true, all other sensitive Socket.IO events (DEVICE_BROWSE, HOST_INTERFACES, DEVICE_TAGS_REQUEST, etc.) call isSocketAdminAuthorized to verify the connection token, but the DAQ_QUERY handler in server/runtime/index.js lacks this check entirely.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-10
Last Modified
2026-08-10
Generated
2026-08-10
AI Q&A
2026-08-10
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
frangoteam fuxa 1.3.3

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-306 The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability is a missing authentication issue in FUXA versions up to 1.3.3. An unauthenticated remote attacker can exploit it by sending a DAQ_QUERY Socket.IO event to retrieve all historical sensor data without proper authorization. While other sensitive events verify admin tokens via isSocketAdminAuthorized(), the DAQ_QUERY handler lacks this security check entirely.

Detection Guidance

To detect this vulnerability, monitor network traffic for unauthorized Socket.IO connections to the DAQ_QUERY event. Check server logs for repeated queries to historical sensor data without authentication tokens. Use tools like Wireshark to inspect Socket.IO traffic on the FUXA server port (default is 1880).

Commands: netstat -tulnp | grep 1880 to check listening ports, ss -tulnp | grep node to find FUXA processes, and tcpdump -i any port 1880 -A to capture Socket.IO traffic.

Impact Analysis

An attacker could access all stored sensor data, potentially exposing sensitive operational or environmental information. This could lead to privacy breaches, industrial espionage, or enable further attacks by understanding system configurations and data patterns.

Compliance Impact

This vulnerability likely violates GDPR and HIPAA requirements for data protection and access controls. GDPR mandates strict access controls for personal data, while HIPAA requires safeguards for protected health information. Unauthorized data access could result in non-compliance penalties and legal consequences.

Mitigation Strategies

Immediately update FUXA to the latest version beyond 1.3.3. If an update is unavailable, restrict network access to the FUXA server using firewalls. Disable the DAQ_QUERY event if not essential. Enable secureEnabled=true in configuration to enforce token checks.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-72586. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart