Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
HIGH severity

FUXA's Unauthenticated Project Data Disclosure Exposes Server-Side Scripts and Device ConfigurationsGHSA-q3w6-q3hc-c5x6

HIGH

GHSA-q3w6-q3hc-c5x6 is a high-severity (CVSS 7.5) CWE-201 vulnerability in fuxa-server. A fix is available for fuxa-server — see the affected versions and patch details below.

Also known asCVE-2026-47717
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Oct 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

  • CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
  • CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.

Exploitation and automatability from CISA’s SSVC triage for GHSA-q3w6-q3hc-c5x6.

EPSS Exploitation Probability

via FIRST.org ↗
1.4%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs71th percentile — riskier than 71% of all scored CVEsHighest risk
0.70%1.09%1.48%1.88%1.2%1.4%1.4%Sep 26Oct 26Oct 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

GHSA-q3w6-q3hc-c5x6 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 384,534 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.

fuxa-servernpm
17downloads / week

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 Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmfuxa-server≥ 1.3.0&&< 1.3.11.3.1npm install fuxa-server@1.3.1

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for fuxa-server, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update fuxa-server to 1.3.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-q3w6-q3hc-c5x6 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How to detect GHSA-q3w6-q3hc-c5x6

A community-maintained Nuclei template exists for this CVE. You can scan for it directly:

nuclei -id ghsa-q3w6-q3hc-c5x6 -u https://target
Template
FUXA 1.3.0 - Unauthenticated ICS/SCADA Project Data Disclosure
Severity
high
Remediation
Upgrade to fuxa-server version 1.3.1 or later.

Template by ProjectDiscovery nuclei-templates (pussycat0x), MIT licensed. View the full template. Scan only systems you are authorised to test.

Frequently Asked Questions

### 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-gen
O3 Security · Impact-Aware SCA

Is GHSA-q3w6-q3hc-c5x6 in your dependencies?

Find it across npm, including transitive dependencies.

FUXA's Unauthenticated Project Data Disclosure Exposes…