Skip to content

GHSA-q3w6-q3hc-c5x6 CVE-2026-47717

FUXA's Unauthenticated Project Data Disclosure Exposes Server-Side Scripts and Device Configurations

High npm
Severity
7.5 / 10
High · CVSS 3.1
Exploit chance (EPSS)
1.38%
Chance of exploitation in the next 30 days. Higher than 72.03% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-201 Insertion of Sensitive Information Into Sent Data
Fix
1.3.1
Upgrade fuxa-server to this version or later

Description

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

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.

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.

Affected versions

npm

PackageVulnerableFixed in
fuxa-server
>= 1.3.0, < 1.3.1
1.3.1

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

fuxa-server npm → 1.3.1

npm
npm install fuxa-server@1.3.1
yarn
yarn add fuxa-server@1.3.1
pnpm
pnpm add fuxa-server@1.3.1

Severity breakdown

CVSS 3.1 7.5

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

Weakness

CWE-201: Insertion of Sensitive Information Into Sent Data

The code transmits data to another actor, but a portion of the data includes sensitive information that should not be accessible to that actor.

How to prevent it
  • Requirements: Specify which data in the software should be regarded as sensitive. Consider which types of users should have access to which types of data.
  • Implementation: Ensure that any possibly sensitive data specified in the requirements is verified with designers to ensure that it is either a calculated risk or mitigated elsewhere. Any information that is not necessary to the functionality should be removed in order to lower both the overhead and the possibility of security sensitive data being sent.
  • System Configuration: Setup default error messages so that unexpected errors do not disclose sensitive information.
  • Architecture and Design: Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-8ghr-w65f-j3qr
FUXA's scheduler API missing admin check enables operator-to-admin escalation via scheduled device actions
Medium Also affects fuxa-server
GHSA-h9fj-c2qr-76g2
FUXA has SQL Injection in its TDengine DAQ connector via backslash bypass of escapeTdString
Medium Also affects fuxa-server
GHSA-w86f-rf9w-h3x6
FUXA: Unauthenticated SSRF via Socket.IO DEVICE_WEBAPI_REQUEST and DEVICE_PROPERTY with response reading
High Also affects fuxa-server
GHSA-r9g5-7q8j-958c
FUXA provides guest and invalid-token access to protected read APIs in secure mode
Medium Also affects fuxa-server
GHSA-rg3m-cfq7-g6h6
FUXA Vulnerable to Unauthenticated Remote Code Execution via Script Test Mode Authorization Bypass
High Also affects fuxa-server
GHSA-fwcm-rqvw-j3p7
FUXA has an unauthenticated arbitrary tag value disclosure via /api/getTagValue
High Also affects fuxa-server
GHSA-68m5-5w2h-h837
FUXA Affected by a Path Traversal Sanitization Bypass
High Also affects fuxa-server
GHSA-c869-jx4c-q5fc
FUXA Unauthenticated Remote Arbitrary Scheduler Write
Critical Also affects fuxa-server
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor