Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-47718

Authentication Bypass in fuxa-server (CVE-2026-47718)

Summary

Authentication bypass in fuxa-server (CVE-2026-47718). Risk of unauthorized operations or information disclosure. Exploitable via GET /api/project. Mitigation: upgrade to 1.3.1 or later.

Original description

The description as published by the source.

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/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…

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-47718 has been found in fuxa-server.
Attackers can target a specific entry point like GET /api/project over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade fuxa-server to 1.3.1 or later.
If unsure, ask your IT team or search "fuxa-server CVE-2026-47718" on the vendor's site.

CVE-2026-47718 (fuxa-server) — CWE-287
Attack surface: GET /api/project / GET /api/alarms / GET /api/scheduler
Patched: 1.3.1 — apply immediately
Workaround: set secure: Enabled
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Authentication bypass (CWE-287) exists in fuxa-server. Attackers reach the vulnerable code path via GET /api/project.

📍 Affected scope

Check the vendor advisory for the affected versions of fuxa-server. Attack surface: GET /api/project / GET /api/alarms / GET /api/scheduler.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 1.3.1.

🛡️ Workaround

Workaround: set secure: Enabled

🔍 Detection

Search webserver/proxy logs for unusual GET /api/project requests with malformed payloads or SQL meta-characters. Run grep -r 'fuxa-server' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'fuxa-server' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で fuxa-server を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Hunt for indicators of compromise detect 
    grep 'GET /api/project' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで GET /api/project への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

  3. 3
    Apply temporary workaround mitigate 
    set secure: Enabled

    パッチが適用されるまでの応急処置として、set secure: Enabled を実施。回避策の副作用 (機能低下) を確認した上で。

  4. 4
    Apply patch patch 
    Upgrade fuxa-server to 1.3.1

    ステージング環境で 1.3.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。

  5. 5
    Post-deployment verification verify 
    Replay attack against GET /api/project on staging to confirm patch closes the vector

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

npm fuxa-server
[{"type":"SEMVER","events":[{"introduced":"1.3.0-2773"},{"fixed":"1.3.1"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details