CVE-2026-47717

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

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):

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:

curl -s http://192.168.32.129:1881/api/project

{
  "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.

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.

CVE-2026-47717 has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.3.1); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2026-47717? CVE-2026-47717 is a high-severity security vulnerability in fuxa-server (npm), affecting versions = 1.3.0. It is fixed in 1.3.1.
2. How severe is CVE-2026-47717? CVE-2026-47717 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of fuxa-server are affected by CVE-2026-47717? fuxa-server (npm) versions = 1.3.0 is affected.
4. Is there a fix for CVE-2026-47717? Yes. CVE-2026-47717 is fixed in 1.3.1. Upgrade to this version or later.
5. Is CVE-2026-47717 exploitable, and should I be worried? Whether CVE-2026-47717 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-47717 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-47717? Upgrade fuxa-server to 1.3.1 or later.