CVE-2026-47718

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/project returned 200 OK
• invalid-token requests to /api/project also returned successful responses containing project data
• guest and invalid-token requests also returned 200 OK on:
  • /api/alarms
  • /api/scheduler

Relevant 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 request
• server/api/projects/index.js
• server/api/alarms/index.js
• server/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:

1. Start FUXA 1.3.0-2773.
2. Set secureEnabled=true.
3. Send unauthenticated requests to:
   • GET /api/project
   • GET /api/alarms
   • GET /api/scheduler?id=test
4. Observe 200 OK responses.
5. Send the same requests with an explicitly invalid x-access-token value.
6. 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.

The application does not adequately verify the identity of a user, device, or process before granting access. Typical impact: unauthorized access to functions or data reserved for authenticated parties.

Kodem intelligence

1. What is CVE-2026-47718? CVE-2026-47718 is a medium-severity improper authentication vulnerability in fuxa-server (npm), affecting versions = 1.3.0-2773. It is fixed in 1.3.1. The application does not adequately verify the identity of a user, device, or process before granting access.
2. Which versions of fuxa-server are affected by CVE-2026-47718? fuxa-server (npm) versions = 1.3.0-2773 is affected.
3. Is there a fix for CVE-2026-47718? Yes. CVE-2026-47718 is fixed in 1.3.1. Upgrade to this version or later.
4. Is CVE-2026-47718 exploitable, and should I be worried? Whether CVE-2026-47718 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
5. What actually determines whether CVE-2026-47718 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
6. How do I fix CVE-2026-47718? Upgrade fuxa-server to 1.3.1 or later.