Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.5amended

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

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

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (fuxa-server 1.3.1), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS
  • CVE-2026-47717: 1.38% estimated exploitation activity in the next 30 days; percentile 72.05 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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 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): 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: No authentication token, API key, or cookie was provided. The response includes: - Server-side…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-q3w6-q3hc-c5x6

  2. Revision 1 · created ·

    Published from osv record GHSA-q3w6-q3hc-c5x6

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-47717

Advisory: FUXA's Unauthenticated Project Data Disclosure Exposes Server-Side Scripts and Device Configurations
IDs: CVE-2026-47717, GHSA-q3w6-q3hc-c5x6
Record: https://patchnext.com/advisories/cve-2026-47717 (revision 2, source checked 26 Oct 2026, 12:52 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: fuxa-server 1.3.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm fuxa-server: affected >= 1.3.0, <= 1.3.0; fixed in 1.3.1

## Suggested inspection (read-only)
- `npm ls fuxa-server --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on fuxa-server.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-q3w6-q3hc-c5x6 (OSV record GHSA-q3w6-q3hc-c5x6 lists affected ranges: npm fuxa-server >=1.3.0 <1.3.1 (fixed))
- Verified: https://github.com/advisories/GHSA-q3w6-q3hc-c5x6 (GitHub-reviewed advisory GHSA-q3w6-q3hc-c5x6 lists affected ranges: npm fuxa-server >=1.3.0 <=1.3.0)

Commands are suggestions: review each one before running it.

Loading voting…