FUXA is a web-based Process Visualization (SCADA/HMI/Dashboard) software. In 1.3.2 and earlier, the allowDashboard authorization gate in server/integrations/node-red/index.js calls authJwt.verify for /nodered without inspecting the decoded identity. When nodeRedEnabled is true, secureEnabled is true, and nodeRedAuthMode is secure, a remote unauthenticated attacker can obtain a signed guest token from POST /api/heartbeat and use it to access the RED.httpAdmin editor and flow deployment API. Because the Node-RED configuration has no second adminAuth gate, the attacker can deploy function nodes or invoke fuxa.runScript and runtime.scriptsMgr.runScript, gaining control of FUXA project data, configuration, scripts, filesystem-capable runtime helpers, and potentially operating-system commands when nodeRedUnsafeModules is enabled. This issue is fixed in version 1.3.3.
Security readout for executives and security teams
Plain-English summary
A remote attacker without an account could use a legitimate guest token to enter FUXA’s Node-RED administration interface under specific configurations. From there, they could alter automation flows, scripts, project data, and configuration, potentially reaching operating-system commands. FUXA versions before 1.3.3 are affected.
Executive priority
Treat affected, reachable installations as an immediate remediation priority, especially where FUXA connects to SCADA, HMI, or operational environments. Upgrade promptly and investigate suspicious Node-RED or script changes. Current sources do not prove exploitation in the wild, but the potential compromise of monitoring, configuration, and host-level capabilities supports critical handling.
Technical view
The /nodered authorization gate verifies a signed JWT but does not confirm that its decoded identity is authorized. A guest JWT obtainable through /api/heartbeat therefore passes the gate when Node-RED and secure mode are configured as described. The exposed editor and deployment API enable remote script execution. This is CWE-862 with CVSS 4.0 score 9.2.
Likely exposure
Exposure requires FUXA before 1.3.3 with nodeRedEnabled and secureEnabled enabled, nodeRedAuthMode set to secure, and /nodered remotely reachable. Impact may expand to operating-system command execution when nodeRedUnsafeModules is enabled. Deployments without these conditions are not established as exploitable by the supplied evidence.
Exploitation context
The vulnerability is remotely reachable, needs no privileges or user interaction, and requires particular configuration conditions. The supplied record states that it is not in KEV, and no cited source establishes active exploitation. Public disclosure and a vendor patch nevertheless make prompt remediation appropriate.
Researcher notes
The authorization failure is identity-blind token validation: signature validity is treated as authorization. The stated attack path depends on guest-token availability and the named Node-RED configuration. The absence of a secondary adminAuth check enables editor and deployment access. Review the vendor commit and pull request for the exact authorization change; avoid assuming other FUXA routes are affected.
Mitigation direction
Upgrade FUXA to version 1.3.3 or later.
Prioritize internet-accessible or operational-technology deployments meeting the vulnerable configuration conditions.
Until upgraded, reduce external access to FUXA and Node-RED administrative routes.
Consult the vendor advisory for any deployment-specific interim guidance.
Review whether nodeRedUnsafeModules is enabled and disable it unless operationally required.
Validation and detection
Inventory FUXA instances and record their installed versions.
Check nodeRedEnabled, secureEnabled, nodeRedAuthMode, and nodeRedUnsafeModules settings.
Confirm that exposed instances no longer run versions earlier than 1.3.3.
Review logs for unexpected guest-token issuance, /nodered access, flow deployment, or script activity.
Validate that Node-RED administration is inaccessible to unauthenticated or guest identities after remediation.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-862: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
5Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-862 · source CWE mapping
Missing Authorization
Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.