Skip to main content

Boteraser | Website and Server Security Solutions

🛡️ CVE-2026-47719 — fuxa-server

🟠 CVSS 8.2 — High ✅ No Known Exploit CWE-918 NVD
8.2
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

FUXA: Unauthenticated SSRF via Socket.IO DEVICE_WEBAPI_REQUEST and DEVICE_PROPERTY with response reading

Summary

An unauthenticated attacker (Alice) connects to FUXA's Socket.IO endpoint and emits a device-webapi-request event whose property.address field names an arbitrary URL. FUXA's DEVICE_WEBAPI_REQUEST handler at server/runtime/index.js:296 calls axios.get(address) server-side and broadcasts the full response body back on the same event via io.emit. The companion handler DEVICE_PROPERTY at server/runtime/index.js:153 has the same miss against OPC UA and ODBC endpoints. Both handlers skip the isSocketWriteAuthorized() check that the other write-capable events (DEVICE_VALUES at line 182, DEVICE_ENABLE at line 358) call. Alice reads cloud instance metadata, scans internal services, and connects to any OPC UA server or ODBC database the FUXA host can reach, then receives the results.

Details

Vulnerable handlers: server/runtime/index.js:153-171, 296-316:

```javascript

socket.on(Events.IoEventTypes.DEVICE_PROPERTY, (message) => {

try {

if (message && message.endpoint && message.type) {

devices.getSupportedProperty(message.endpoint, message.type).then(result => {

message.result = result;

io.emit(Events.IoEventTypes.DEVICE_PROPERTY, message);

})

// ...

}

}

// ...

});

socket.on(Events.IoEventTypes.DEVICE_WEBAPI_REQUEST, (message) => {

try {

if (message && message.property) {

devices.getRequestResult(message.property).then(result => {

message.result = result;

io.emit(Events.IoEventTypes.DEVICE_WEBAPI_REQUEST, message);

})

// ...

}

}

// ...

});

```

Sink: server/runtime/devices/httprequest/index.js:471 for the webapi path:

```javascript

if (property.method === 'GET') {

axios.get(property.address).then(res => {

resolve(res.data);

// ...

```

Alice fully controls property.address, and io.emit echoes the response body back on the same event. For the ODBC variant, server/runtime/devices/odbc/index.js builds the connection string from endpoint.address plus endpoint.uid and endpoint.pwd, so Alice supplies credentials and targets any reachable ODBC server.

Contrast: server/runtime/index.js:182 (the DEVICE_VALUES write handler) gates the exact same kind of action behind isSocketWriteAuthorized(socket). The two handlers above skip that check.

Reachability: neither handler performs any authorization check, so both modes reach the sinks. secureEnabled=true does not close the gap because the Socket.IO connect block at server/runtime/index.js:114-120 auto-issues a guest token to any client that connects without one, and the handlers run regardless of socket.isAuthenticated. This is the same pattern GHSA-vwcg-c828-9822's note warned about: enabling authentication does not mitigate the missing check here.

Impact

Alice uses FUXA as a read-SSRF oracle against any HTTP(S) service the FUXA host can reach, with the response body delivered back to her Socket.IO session. On cloud-hosted SCADA deployments this exfiltrates IAM credentials from the instance metadata service. On OT networks it reaches internal OPC UA servers, ODBC databases, and administrative consoles that have no other external exposure. The ODBC variant accepts attacker-supplied credentials, so Alice authenticates to any ODBC server that trusts connections from the FUXA host. The attack works against secureEnabled=true deployments as well as the default; no operator interaction required.

CVSS 3.1: AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N (High, 8.2). CWE-918.

Recommended Fix

Add the existing isSocketWriteAuthorized(socket) check at the top of both handlers, matching the pattern used by DEVICE_VALUES and DEVICE_ENABLE. Also switch io.emit to socket.emit so the response scopes to the requesting socket instead of broadcasting to every connected client. For defense in depth, validate property.address against an allowlist of schemes and reject private, loopback, and link-local address ranges before calling axios.get or the device connect paths.

```javascript

socket.on(Events.IoEventTypes.DEVICE_WEBAPI_REQUEST, (message) => {

try {

if (!isSocketWriteAuthorized(socket)) {

logger.warn(${Events.IoEventTypes.DEVICE_WEBAPI_REQUEST}: unauthorized request from ${socket.userId || 'guest'});

return;

}

if (message && message.property) {

// ... validate property.address against allowlist ...

devices.getRequestResult(message.property).then(result => {

message.result = result;

socket.emit(Events.IoEventTypes.DEVICE_WEBAPI_REQUEST, message);

})

// ...

}

}

// ...

});

```

Apply the same three changes (auth check, socket.emit, address

How this vulnerability can be exploited

This issue can be reached over the network, attack complexity is low, an attacker needs no privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality high, integrity low, availability none.

CVSS metrics in full

The score comes from this vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N

  • Attack vector: Network — reachable from anywhere that can route to the service.
  • Attack complexity: Low — the attack works reliably, with no preparation.
  • Privileges required: None — an unauthenticated stranger can try it.
  • User interaction: None — nobody has to be tricked into anything.
  • Scope: Unchanged — the damage stays inside the vulnerable component.
  • Confidentiality impact: High — total loss, or loss the attacker controls.
  • Integrity impact: Low — limited, and the attacker does not choose what is affected.
  • Availability impact: None.

Weakness class

CVE-2026-47719 is classified as CWE-918: Server-Side Request Forgery (SSRF). The server fetches a URL supplied by the caller, which can be pointed at internal systems it alone can reach.

Affected software

CVE-2026-47719 is recorded against 2 packages.

  • fuxa-server
  • unknown

Timeline and source

Published on 8 June 2026. No public exploit is currently recorded for this entry. Record sourced from NVD.

References

github.com (Web)
github.com (Package)
github.com (Web)

Other advisories for this package

fuxa-server has other advisories on record. If you are patching this one, these are worth checking on the same host:

Same weakness in other software

These advisories are the same class of weakness (CWE-918: Server-Side Request Forgery (SSRF)) in other software:

Details

Severity HIGH
CVSS Score 8.2
CVSS Vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
CWE CWE-918
Public Exploit ✅ No
Source NVD
Published 2026-06-08
Updated 2026-08-20
Modified 2026-06-08
Fix URL N/A

Affected Packages

Software From version Fixed in
fuxa-server
unknown

Similar Threats

Site Security Check

Is fuxa-server part of your stack?

CVE-2026-47719 is rated CVSS 8.2 High. BotEraser scans your installation against known CVE records and tells you whether this vulnerability applies to the versions you actually run.

Scan My Site Free →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.

Browse related advisories

All advisoriesCVECVE 2026