dbcve.org
FuxaApplication · Frangoteam

CVE-2026-25893

CRITICAL · 9.8 CVSS v3.1 Published 2026-02-09
Fix available
A fix is available. Upgrade to 1.2.10 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. Prior to 1.2.10, an authentication bypass vulnerability in FUXA allows an unauthenticated, remote attacker to gain administrative access via the heartbeat refresh API and execute arbitrary code on the server. This issue has been patched in FUXA version 1.2.10.

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 prior to 1.2.10 contain an authentication bypass vulnerability in the heartbeat refresh API that allows unauthenticated remote attackers to gain administrative access and execute arbitrary code on the server.

MitigationUpgrade FUXA to version 1.2.10 or later to remediate the authentication bypass. In SCADA/HMI environments, validate the upgrade in a test environment before production deployment due to potential operational impacts.

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.10

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. Confirm FUXA is installed on the system
    Check for FUXA process running or look for FUXA installation directories (commonly in /opt/fuxa, /var/www/fuxa, or user home directories). Use commands like 'ps aux | grep fuxa' or 'netstat -tlnp' to find listening services.
    Affected if FUXA process or installation is found on the system
  2. Determine installed FUXA version
    Locate the package.json file in the FUXA installation directory and check the 'version' field. Alternatively, check the server response when accessing the FUXA web interface for version information.
    Affected if The installed version is lower than 1.2.10 (e.g., 1.2.9, 1.2.8, etc.)
  3. Check if heartbeat refresh API is externally accessible
    Identify the API endpoint path for heartbeat refresh (typically /api/heartbeat or similar). Test accessing this endpoint without authentication credentials using curl or a browser developer tool.
    Affected if The heartbeat API endpoint responds without requiring authentication
  4. Review user accounts for unauthorized administrative access
    Log into the FUXA web interface and navigate to the user management section. Check for any unexpected admin-level accounts that were not created by legitimate administrators.
    Affected if Unexpected admin accounts exist or account creation timestamps correlate with potential exploitation period

The environment is affected if FUXA version is below 1.2.10 AND the heartbeat refresh API is accessible without authentication.

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.10 or later
Fixed in 1.2.10
Vendor patch github.com →
Interim mitigation

Upgrade FUXA to version 1.2.10 or later to remediate the authentication bypass. In SCADA/HMI environments, validate the upgrade in a test environment before production deployment due to potential operational impacts.

Recommended fix High confidence

FUXA version 1.2.10

  1. Back up the current FUXA installation and configuration data
  2. Stop the running FUXA service
  3. Download FUXA version 1.2.10 from the official GitHub repository (github.com/frangoteam/FUXA/releases)
  4. Replace the existing FUXA installation files with the new version 1.2.10
  5. Apply any backed-up configuration to the new installation
  6. Start the FUXA service
  7. Verify the heartbeat refresh API now properly requires authentication and cannot be accessed without credentials
  8. Test that the application functions normally with proper authentication enforced

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

Fix this in Fuxa Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Get it on GitHub Scan in the browser

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-25893 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