Vulnerability in fuxa-server (CVE-2026-47717)
Summary
Vulnerability in fuxa-server (CVE-2026-47717). Confidential information can be exposed externally. Exploitable via GET /api/project. Mitigation: upgrade to 1.3.1 or later.
Original description
The description as published by the source.
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
prjApp.get("/api/project", secureFnc, function(req, res) {
const permission = checkGroupsFnc(req);
runtime.project.getProject(req.userId, permission).then(result => {
if (result) {
res.json(result);
}
});
});
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):
if (!token) {
token = getGuestToken();
}
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: truewith a randomsecretCode
Retrieve full project data without authentication:
curl -s http://192.168.32.129:1881/api/project
{
"scripts": [
{
"id": "SCRIPT_ID",
"name": "calculate"
},
]
}
No authentication token, API key, or cookie was provided.…
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-47717 has been found in fuxa-server.
Attackers can target a specific entry point like GET /api/project over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 7.5/10.
What to do: upgrade fuxa-server to 1.3.1 or later.
If unsure, ask your IT team or search "fuxa-server CVE-2026-47717" on the vendor's site.
CVE-2026-47717 (fuxa-server) — CWE-201 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: GET /api/project / secureFnc / verifyToken / getProject
Patched: 1.3.1 — apply immediately
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.
A vulnerability (CWE-201) exists in fuxa-server. Attackers reach the vulnerable code path via GET /api/project without authentication.
Check the vendor advisory for the affected versions of fuxa-server. Attack surface: GET /api/project / secureFnc / verifyToken / getProject.
Severity: High (CVSS 7.5/10). Confidential information can be exposed externally.
Update to 1.3.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
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
-
1Identify exposure identify
grep -r 'fuxa-server' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
fuxa-serverを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt 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 があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade fuxa-server to 1.3.1ステージング環境で 1.3.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against GET /api/project on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- package github.com
- web github.com
- web security-advisories@github.com
- web github.com