Skip to main content

FUXA CVE-2026-47717

HIGH
Insertion of Sensitive Information Into Sent Data (CWE-201)
2026-05-27 https://github.com/frangoteam/FUXA GHSA-q3w6-q3hc-c5x6
7.5
CVSS 3.1
Share

CVSS VectorNVD

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

Lifecycle Timeline

2
Source Code Evidence Fetched
May 27, 2026 - 23:17 vuln.today
Analysis Generated
May 27, 2026 - 23:17 vuln.today

DescriptionNVD

Summary

The GET /api/project endpoint exposes sensitive project configuration data to guest-context requests even when secureEnabled is enabled.

Details

File: server/api/projects/index.js

javascript
prjApp.get("/api/project", secureFnc, function(req, res) {
    const permission = checkGroupsFnc(req);
    runtime.project.getProject(req.userId, permission).then(result => {
        if (result) {
            res.json(result);
        }
    });
});

The endpoint uses the secureFnc middleware, but this middleware calls verifyToken in server/api/jwt-helper.js which auto-generates a valid guest JWT when no token is provided (line 49-51):

javascript
if (!token) {
    token = getGuestToken();
}

The guest token is signed with the server's secret and passes verification. The handler then calls getProject which returns the full project data. The _filterProjectPermission function (line 924 of server/runtime/project/index.js) filters some UI elements for non-admin users, but it does not remove scripts, devices, alarms, or other sensitive configuration data.

PoC

Environment

  • FUXA v1.3.0-2773 (frangoteam/fuxa:latest)
  • secureEnabled: true with a random secretCode

Retrieve full project data without authentication:

bash
curl -s http://192.168.32.129:1881/api/project
json
{
  "scripts": [
    {
      "id": "SCRIPT_ID",
      "name": "calculate"
    },
  ]
}

No authentication token, API key, or cookie was provided. The response includes:

  • Server-side scripts: full source code, IDs, names, execution mode, and permission levels. This reveals internal automation logic and sensitive project structure information that could assist further attacks against the deployed system.
  • Device configurations: and communication endpoint information may also be exposed depending on the deployed project configuration.
  • HMI views: the full SVG content and layout of every operator screen, including variable bindings that map UI elements to device tags.
  • Alarm definitions: alarm thresholds, conditions, and notification settings when configured.

Impact

The endpoint may expose sensitive project configuration data including script metadata, device connection information, HMI configuration, and alarm definitions. In industrial environments this information can assist further targeted attacks against the deployed system.

AnalysisAI

Unauthenticated information disclosure in FUXA 1.3.0 (web-based SCADA/HMI server, npm package fuxa-server) lets remote attackers retrieve full project configuration from the GET /api/project endpoint even when secureEnabled is turned on. The exposed data includes server-side script source code, device connection details, HMI view layouts with tag bindings, and alarm definitions. …

Sign in for full analysis, threat intelligence, and remediation guidance.

RemediationAI

Within 24 hours: Inventory all fuxa-server 1.3.0 deployments and verify /api/project endpoint accessibility from untrusted networks; review access logs for suspicious project endpoint requests. Within 7 days: Implement firewall or WAF rules restricting /api/project to authorized IP ranges; conduct impact assessment of exposed configurations (source code, credentials, device details) for each instance. …

Sign in for detailed remediation steps.

Share

CVE-2026-47717 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy