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.
Published May 28, 2026
Affected packages
fuxa-server
- Ecosystem
- npm
- Affected
- = 1.3.0-2773
- Fixed in
- 1.3.1
- Check
npm ls fuxa-server
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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:
- guest
GET /api/projectreturned200 OK - invalid-token requests to
/api/projectalso returned successful responses containing project data - guest and invalid-token requests also returned
200 OKon: /api/alarms/api/scheduler
Relevant code paths identified during analysis:
server/api/jwt-helper.jsverifyToken()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.js
These 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:
- Start FUXA
1.3.0-2773. - Set
secureEnabled=true. - Send unauthenticated requests to:
GET /api/projectGET /api/alarmsGET /api/scheduler?id=test- Observe
200 OKresponses. - Send the same requests with an explicitly invalid
x-access-tokenvalue. - Observe the same successful responses.
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:
- project metadata disclosure
- alarms disclosure
- scheduler information disclosure
- assistance in reconnaissance/follow-on attacks
Operators who believe secure mode protects these APIs are impacted.
Credited to north-echo.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-47719
FUXA: Unauthenticated SSRF via Socket.IO DEVICE_WEBAPI_REQUEST and DEVICE_PROPERTY with response reading
high8.2No fixJun 8, 2026CVE-2026-47720
FUXA has SQL Injection in its TDengine DAQ connector via backslash bypass of escapeTdString
medium5.3No fixJun 8, 2026CVE-2026-47721
FUXA's scheduler API missing admin check enables operator-to-admin escalation via scheduled device actions
medium6.3No fixJun 8, 2026CVE-2026-47717
FUXA's Unauthenticated Project Data Disclosure Exposes Server-Side Scripts and Device Configurations
high7.5May 27, 2026CVE-2026-43946
FUXA has an unauthenticated arbitrary tag value disclosure via /api/getTagValue
high7.7May 26, 2026CVE-2026-43947
FUXA Vulnerable to Unauthenticated Remote Code Execution via Script Test Mode Authorization Bypass
high8.9May 26, 2026
