CVE-2026-65984
HighCVSS 7.5Exploitation Probability (EPSS)
Low risk39th percentile - higher than 39% of all known CVEs
Summary
FUXA version 1.3.2 and earlier improperly handled session refresh, allowing an attacker with a previously issued privileged refresh cookie or access token to continue minting privileged JWTs even after account deletion, disablement, role removal, or demotion. This enabled continued unauthorized access to user management, project manipulation, runtime configuration, and backdoor-account creation. The issue is fixed in version 1.3.3.
Risk Assessment
The risk includes maintaining unauthorized access to the system, potentially leading to full control of the SCADA/HMI system, configuration changes, or creation of backdoor accounts.
Recommendation
Upgrade FUXA to version 1.3.3 or later and invalidate all existing sessions and tokens. Also review user accounts for unauthorized changes.
Other vulnerabilities in FUXA
See all- CVE-2026-67443Critical
FUXA version 1.3.2 and earlier has a vulnerability in the allowDashboard authorization gate that allows a remote unauthenticated attacker to obtain a signed guest token and access the Node-RED editor and flow deployment API. The attacker can deploy malicious nodes or execute scripts, gaining control over project data, configuration, and potentially the operating system.
- CVE-2026-67442Low
FUXA is a web-based Process Visualization (SCADA/HMI/Dashboard) software. Prior to 1.3.3, DELETE /api/roles removes role definitions but does not remove the deleted role identifier from user's info.roles array or runtime usersMap cache. This can lead to retained authorization rights after admin revocation.
- CVE-2026-67440Medium
FUXA version 1.3.2 and earlier does not check isSocketAdminAuthorized for certain Socket.IO events (DEVICE_BROWSE, DEVICE_NODE_ATTRIBUTE, HOST_INTERFACES, DEVICE_TAGS_REQUEST) when secureEnabled is true. A remote unauthenticated or guest user can collect system-discovery information not required for normal HMI viewing.
- CVE-2026-65985Medium
FUXA version 1.3.2 and earlier allows an authenticated non-admin user to control property.address in the device-webapi-request handler, causing the FUXA server to issue outbound HTTP/HTTPS requests and return the response to the attacker. This leads to an SSRF vulnerability.
- CVE-2026-47721Medium
FUXA is a web-based Process Visualization (SCADA/HMI/Dashboard) software. Prior to 1.3.2, POST /api/scheduler and DELETE /api/scheduler do not consistently enforce admin permissions. An authenticated non-admin operator can create or alter deviceActions or delete schedules, gaining access to device-value changes and server-side script execution.
- CVE-2026-47720Medium
FUXA is a web-based Process Visualization (SCADA/HMI/Dashboard) software. Prior to 1.3.2, the escapeTdString function does not escape backslashes, allowing a remote unauthenticated attacker to inject SQL via crafted sids tag identifiers. This can expose historical PLC tag values and device names.
- CVE-2026-47719High
FUXA before version 1.3.2 has a vulnerability allowing a remote unauthenticated attacker to perform SSRF (Server-Side Request Forgery) via the DEVICE_WEBAPI_REQUEST and DEVICE_PROPERTY Socket.IO handlers. By manipulating property.address or endpoint connection data, the attacker can make the server call axios.get against arbitrary HTTP/HTTPS destinations, including internal services, cloud metadata, OPC UA, or ODBC services. The issue is fixed in version 1.3.2.
- CVE-2026-47718Medium
FUXA is a web-based Process Visualization (SCADA/HMI/Dashboard) software. When `secureEnabled=true`, FUXA `1.3.0-2773` still allows guest and invalid-token requests to read project, alarms, and scheduler APIs. Version 1.3.1 fixes this issue.
- CVE-2026-47717High
FUXA is a web-based Process Visualization (SCADA/HMI/Dashboard) software. In fuxa-server version 1.3.0, the GET /api/project endpoint exposes sensitive project configuration data to guest-context requests even when secureEnabled is enabled. Version 1.3.1 fixes the issue.
- CVE-2026-72586High
A missing authentication vulnerability in 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.
Original NVD description (English source)
FUXA is a web-based Process Visualization (SCADA/HMI/Dashboard) software. In 1.3.2 and earlier, POST /api/refresh in server/api/auth/index.js falls back from current user data to decoded.groups, including when the user is deleted or groups is zero, and POST /api/heartbeat in server/api/index.js re-signs inbound JWT claims without validating the current database record. An attacker who possesses a previously issued privileged refresh cookie or access token can continue minting privileged JWTs after account deletion, disablement, role removal, or demotion. Continued refresh-cookie rotation can extend the stale session and preserve unauthorized access to user management, project manipulation, runtime configuration, scripts, and backdoor-account creation. This issue is fixed in version 1.3.3.
Vulnerability data from NVD (NIST) · CISA KEV · EPSS

