Authorization Flaw in fuxa-server (CVE-2026-43946)
Summary
Vulnerability in fuxa-server (CVE-2026-43946). Risk of unauthorized operations or information disclosure. Exploitable via req.userId. Mitigation: upgrade to 1.3.1 or later.
Original description
The description as published by the source.
FUXA is a web-based Process Visualization (SCADA/HMI/Dashboard) software. Version 1.3.0 has an authorization bypass in the /api/getTagValue endpoint allows unauthenticated access to tag values when the referenced script does not exist. Version 1.3.1 patches the issue.
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-43946 has been found in fuxa-server.
Attackers can target a specific entry point like req.userId 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-43946" on the vendor's site.
CVE-2026-43946 (fuxa-server) — CWE-863
Attack surface: req.userId / req.userGroups / true / guest
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.
Incorrect authorization (CWE-863) exists in fuxa-server. Attackers reach the vulnerable code path via req.userId.
Check the vendor advisory for the affected versions of fuxa-server. Attack surface: req.userId / req.userGroups / true / guest.
Severity: ?. Risk of unauthorized operations or information disclosure.
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 request patterns matching this CVE's known IOCs. 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 し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade fuxa-server to 1.3.1ステージング環境で 1.3.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- patch github.com
- patch github.com
- web github.com
- web github.com