← Back
CVE-2026-47719
high
CVSS 8.2
SSRF (Server-Side Request Forgery) in fuxa-server (CVE-2026-47719)
Summary
SSRF in fuxa-server (CVE-2026-47719). Confidential information can be exposed externally. Exploitable via ``property.address``.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-47719** has been found in fuxa-server.
Attackers can target a specific entry point like ``property.address`` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 8.2/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "fuxa-server CVE-2026-47719" on the vendor's site.
CVE-2026-47719 (fuxa-server) — CWE-918 / CVSS v3 8.2
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `property.address` / `DEVICE_WEBAPI_REQUEST` / `io.emit` / `DEVICE_PROPERTY`
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
**SSRF** (CWE-918) exists in fuxa-server. Attackers reach the vulnerable code path via ``property.address`` without authentication.
📍 Affected scope
fuxa-server — . Attack surface: `property.address` / `DEVICE_WEBAPI_REQUEST` / `io.emit` / `DEVICE_PROPERTY`.
🔥 Severity
Severity: High (CVSS 8.2/10). Confidential information can be exposed externally
🔧 How to fix
Update to the patched release per vendor advisory.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
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 (7 steps)
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 し、稼働しているサービス・バージョンを把握する。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
fuxa-server
[{"type":"SEMVER","events":[{"introduced":"0"},{"last_affected":"1.1.14-1243"}]}]