FuxaApplication · Frangoteam

CVE-2026-25938

CRITICAL · 9.8 CVSS v3.1 Published 2026-02-09
Fix available
A fix is available. Upgrade to 1.2.11 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
FUXA is a web-based Process Visualization (SCADA/HMI/Dashboard) software. From 1.2.8 through 1.2.10, an authentication bypass vulnerability in FUXA allows an unauthenticated, remote attacker to execute arbitrary code on the server when the Node-RED plugin is enabled. This has been patched in FUXA version 1.2.11.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

FUXA versions 1.2.8 through 1.2.10 contain an authentication bypass vulnerability in the Node-RED plugin that allows unauthenticated remote attackers to execute arbitrary code on the server. This is a critical-severity vulnerability (CVSS 9.8) specifically affecting deployments where the Node-RED plugin is enabled.

MitigationUpgrade to FUXA version 1.2.11 or later. If immediate upgrading is not feasible, disable the Node-RED plugin as a temporary compensating control.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
FuxaApplication
Affected:>= 1.2.8, < 1.2.11

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed FUXA version
    Locate the FUXA version through the web interface, configuration files, or application metadata
    Affected if version is 1.2.8, 1.2.9, or 1.2.10
  2. Determine Node-RED plugin status
    Check FUXA configuration or plugin settings to verify if the Node-RED plugin is enabled
    Affected if Node-RED plugin is enabled

Environment is affected if FUXA version is between 1.2.8 and 1.2.10 inclusive AND the Node-RED plugin is enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.2.11 or later
Fixed in 1.2.11
Vendor patch github.com →
Interim mitigation

Upgrade to FUXA version 1.2.11 or later. If immediate upgrading is not feasible, disable the Node-RED plugin as a temporary compensating control.

Recommended fix High confidence

FUXA version 1.2.11

  1. Upgrade FUXA to version 1.2.11 or later to patch the authentication bypass vulnerability
  2. If immediate upgrade is not possible, disable the Node-RED plugin as a temporary mitigation until upgrade can be performed
  3. After upgrading, verify that the Node-RED plugin functions correctly with the new version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Fuxa Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-25938 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-25938 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data