Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-47719 – Unauthenticated SSRF – FUXA versions up to and including 1.3.1

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-47719 is a high-severity (CVSS 8.2) Server-Side Request Forgery (SSRF) vulnerability in FUXA, an open-source web-based SCADA/HMI/Dashboard platform. Unauthenticated attackers can abuse two Socket.IO event handlers to force the FUXA server to make arbitrary outbound HTTP requests and connect to internal industrial protocol endpoints, then have the responses relayed back to them.

Technical details

  • Root cause: the DEVICE_WEBAPI_REQUEST and DEVICE_PROPERTY Socket.IO event handlers (server/runtime/index.js, around lines 153–171 and 296–316) do not call the isSocketWriteAuthorized() check that other write-capable Socket.IO events enforce.
  • Trigger: an attacker connects to the FUXA Socket.IO endpoint without any credentials and emits a device-webapi-request event, supplying an arbitrary destination in the property.address field.
  • Attack vector: the server executes axios.get(address) against the attacker-supplied URL, and the DEVICE_PROPERTY handler similarly performs unauthenticated operations against configured OPC UA and ODBC endpoints; the full response is then broadcast back to the client over the same Socket.IO event.
  • Impact: exposure of cloud instance metadata, unauthorized scanning/access to internal network services, and interaction with backend OPC UA servers or ODBC databases reachable from the FUXA host, without any authentication.

Affected software

  • FUXA (frangoteam/FUXA) — all versions up to and including 1.3.1

Severity

  • CVSS v3.1 Base Score: 8.2 (High)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N

Mitigation and recommended actions

  • Immediate: Upgrade to FUXA version 1.3.2 or later, which adds the missing authorization check to these handlers.
  • If patching is not immediately possible: restrict network access to the FUXA Socket.IO endpoint to trusted hosts only, place the application behind a properly authenticated reverse proxy, and monitor/restrict outbound connections from the FUXA host to prevent it from reaching sensitive internal services (cloud metadata endpoints, OPC UA servers, ODBC databases, admin interfaces).

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge