# CVE-2026-25751: FUXA Unauthenticated Exposure of Plaintext Database Credentials

> Unauthenticated attackers can retrieve plaintext database credentials from FUXA, enabling full access to historical process data and potential denial of service.

- **Severity:** Critical 9.1 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Feb 2026
- **Updated:** 9 Feb 2026
- **Also known as:** GHSA-c5gq-4h56-4mmx

## What is CVE-2026-25751?

CVE-2026-25751 is a critical vulnerability in frangoteam FUXA, published on 6 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-312 (Cleartext Storage of Sensitive Information), CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2026-25751?

2 open source packages ship an affected version, including fuxa-server. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `fuxa-server` | npm | All versions | 1.2.10 |
| `fuxa-server` | npm | All versions | 1.2.10 |

Products: Frangoteam Fuxa.

## How do I fix CVE-2026-25751?

Upgrade fuxa-server to 1.2.10 or later.

## Is CVE-2026-25751 being exploited?

There is no known exploitation of CVE-2026-25751 in the wild and no public exploit code.

## Other vulnerabilities in frangoteam FUXA

- [CVE-2026-25893](https://insights.sbomify.com/CVE-2026-25893/): FUXA Unauthenticated Remote Code Execution via Admin JWT Minting (critical 10.0)
- [CVE-2025-69985](https://insights.sbomify.com/CVE-2025-69985/): FUXA has JWT Authentication Bypass via HTTP Referer header spoofing (critical 9.8)
- [CVE-2025-69971](https://insights.sbomify.com/CVE-2025-69971/): FUXA has a hardcoded fallback JWT signing secret (critical 9.8)
- [CVE-2023-31719](https://insights.sbomify.com/CVE-2023-31719/): FUXA SQL Injection vulnerability (critical 9.8)
- [CVE-2023-33831](https://insights.sbomify.com/CVE-2023-33831/): A remote command execution (RCE) vulnerability in the /api/runscript endpoint of FUXA (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-25751 and fix it if it is affected.

What it is: CVE-2026-25751 is a critical vulnerability in frangoteam FUXA, published on 6 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-25751 in the wild and no public exploit code.

Affected packages and fixed versions:
- fuxa-server (npm): affected all versions; fixed in 1.2.10
- fuxa-server (npm): affected all versions; fixed in 1.2.10

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-25751/ (Markdown: https://insights.sbomify.com/CVE-2026-25751/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-25751
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-25751
- OSV: https://osv.dev/vulnerability/CVE-2026-25751

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-25751/
Summaries are generated and may contain mistakes; the official description above is the record.