dbcve.org
FuxaApplication · Frangoteam

CVE-2026-25751

HIGH · 7.5 CVSS v3.1 Published 2026-02-06
Fix available
A fix is available. Upgrade to 1.2.10 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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. An information disclosure vulnerability in FUXA allows an unauthenticated, remote attacker to retrieve sensitive administrative database credentials. Exploitation allows an unauthenticated, remote attacker to obtain the full system configuration, including administrative credentials for the InfluxDB database. Possession of these credentials may allow an attacker to authenticate directly to the database service, enabling them to read, modify, or delete all historical process data, or perform a Denial of Service by corrupting the database. This affects FUXA through version 1.2.9. 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 1.2.9 and earlier contain an unauthenticated information disclosure vulnerability that exposes InfluxDB database administrative credentials through the system configuration. An unauthenticated remote attacker can directly retrieve these credentials without any authentication, enabling full database access.

MitigationUpgrade FUXA to version 1.2.10 or later to patch the vulnerability. Until patched, network access to FUXA should be restricted and InfluxDB credentials should be rotated.

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
None
Availability
None

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

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 installation and check the version number in package.json, version file, or about page in the web UI. FUXA typically stores version info in the root directory or can be viewed through the application interface.
    Affected if The installed version is 1.2.9 or earlier (any version below 1.2.10)
  2. Confirm InfluxDB integration is configured
    Check the FUXA configuration files (typically in the settings or config directory) for InfluxDB connection settings. Look for influxdb, database, or similar configuration sections that define InfluxDB host, port, username, and password fields.
    Affected if InfluxDB is configured and connected to FUXA - the vulnerability only exposes InfluxDB credentials when this integration exists
  3. Verify web interface accessibility
    Attempt to access the FUXA web interface over HTTP/HTTPS from a browser or curl command without providing any authentication credentials.
    Affected if The web interface is reachable without authentication - this is required for an unauthenticated attacker to exploit the flaw
  4. Check for credential exposure in configuration endpoint
    Inspect any API endpoint that returns system configuration data (commonly /api/settings, /api/config, or similar) without authentication. Use a tool like curl or browser developer tools to examine if InfluxDB credentials are returned in plain text.
    Affected if Configuration API responses contain InfluxDB username and password in plaintext or easily decoded format without requiring authentication

You are affected if FUXA version is below 1.2.10 AND InfluxDB is configured AND the web interface is accessible without authentication, allowing any remote user to retrieve database credentials.

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
Interim mitigation

Upgrade FUXA to version 1.2.10 or later to patch the vulnerability. Until patched, network access to FUXA should be restricted and InfluxDB credentials should be rotated.

Recommended fix High confidence

FUXA version 1.2.10

  1. 1. Back up the current FUXA installation directory and configuration files before proceeding
  2. 2. Stop the FUXA service if it is currently running
  3. 3. Download FUXA version 1.2.10 from the official GitHub repository releases
  4. 4. Replace the existing FUXA installation files with the new version 1.2.10 files
  5. 5. Restart the FUXA service
  6. 6. Verify the application is running correctly and accessible
  7. 7. Confirm the vulnerability is patched by checking that authentication is now required for accessing sensitive endpoints

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

Fix this in Fuxa Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
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,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-25751 — 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-25751 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