Vulnerability in FUXA (CVE-2026-67442)
Summary
Vulnerability in FUXA (CVE-2026-67442). Risk of unauthorized operations or information disclosure. Exploitable via DELETE /api/roles.
Original description
The description as published by the source.
FUXA is a web-based Process Visualization (SCADA/HMI/Dashboard) software. Prior to 1.3.3, DELETE /api/roles removes role definitions through server/runtime/users/usrstorage.js but does not remove the deleted role identifier from each user's info.roles array or the runtime usersMap cache. If a permission configuration still references that identifier, an affected user can retain authorization rights that an administrator intended to revoke, causing residual privilege, inconsistent access-control state, and misleading audit results. This issue is fixed in version 1.3.3.
Source: NIST National Vulnerability Database NVD
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-67442 has been found in FUXA.
Attackers can target a specific entry point like DELETE /api/roles over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 2.0/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "FUXA CVE-2026-67442" on the vendor's site.
CVE-2026-67442 (FUXA) — CWE-284 / CVSS v3 2.0
Attack vector: remote (network-reachable)
Attack surface: DELETE /api/roles
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-284) exists in FUXA. Attackers reach the vulnerable code path via DELETE /api/roles.
Check the vendor advisory for the affected versions of FUXA. Attack surface: DELETE /api/roles.
Severity: Low (CVSS 2.0/10). Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual DELETE /api/roles requests with malformed payloads or SQL meta-characters. Run grep -r 'FUXA' . 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' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
FUXAを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'DELETE /api/roles' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
DELETE /api/rolesへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Post-deployment verification verify
Replay attack against DELETE /api/roles on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。