fuxa-server
Affected
- introduced
1.3.0-2773, fixed1.3.1(semver)
Fixed versions
1.3.1
Fix
- Fixed version
1.3.1npm install [email protected]
Advisory
Also known as: CVE-2026-47718
FUXA provides guest and invalid-token access to protected read APIs in secure mode
Summary
When secureEnabled=true, FUXA 1.3.0-2773 still allows guest and invalid-token requests to read project, alarms, and scheduler APIs.
### Details
In secure mode, requests with no token or an explicitly invalid token were still able to access protected read endpoints.
Confirmed behavior:
GET /api/project returned 200 OK/api/project also returned successful responses containing project data200 OK on: - /api/alarms - /api/schedulerRelevant code paths identified during analysis:
server/api/jwt-helper.js - verifyToken() converts missing-token or invalid-token states into guest context instead of rejecting the requestserver/api/projects/index.jsserver/api/alarms/index.jsserver/api/scheduler/index.jsThese handlers accepted the guest context and returned sensitive data in secure mode.
### PoC
Tested only against isolated local lab instances under the original tester's control. No production, customer, shared, or third-party systems were involved.
Reproduction:
1.3.0-2773.secureEnabled=true.GET /api/project - GET /api/alarms - GET /api/scheduler?id=test200 OK responses.x-access-token value.The exact HTTP requests and local PoC script used for confirmation can be provided upon request.
### Impact
This is an authentication/authorization weakness in secure mode.
Impact includes:
Operators who believe secure mode protects these APIs are impacted.
Medium Basis: The source's own band: MODERATE
1.3.0-2773, fixed 1.3.1 (semver)1.3.1
1.3.1npm install [email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0