CVE-2026-25751 Vulnerability Analysis & Exploit Details

CVE-2026-25751
Vulnerability Scoring

7.5
/10
Very High Risk

Highly exploitable, CVE-2026-25751 poses a critical security risk that could lead to severe breaches.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: None
    No privileges are required for exploitation.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2026-25751 Details

Status: Analyzed

Last updated: 🕝 10 Feb 2026, 14:33 UTC
Originally published on: 🕖 06 Feb 2026, 19:16 UTC

Time between publication and last update: 3 days

CVSS Release: version 3

CVSS3 Source

nvd@nist.gov

CVSS3 Type

Primary

CVSS3 Vector

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

CVE-2026-25751 Vulnerability Summary

CVE-2026-25751: 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.

Assessing the Risk of CVE-2026-25751

Access Complexity Graph

The exploitability of CVE-2026-25751 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2026-25751

With low attack complexity and no required privileges, CVE-2026-25751 is an easy target for cybercriminals. Organizations should prioritize immediate mitigation measures to prevent unauthorized access and data breaches.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2026-25751, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2026-25751, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: High
    Exploiting CVE-2026-25751 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: None
    CVE-2026-25751 poses no threat to data integrity.
  • Availability: None
    CVE-2026-25751 does not impact system availability.

CVE-2026-25751 References

External References

CWE Common Weakness Enumeration

CWE-312

CAPEC Common Attack Pattern Enumeration and Classification

  • Retrieve Embedded Sensitive Data CAPEC-37 An attacker examines a target system to find sensitive data that has been embedded within it. This information can reveal confidential contents, such as account numbers or individual keys/credentials that can be used as an intermediate step in a larger attack.

Vulnerable Configurations

  • cpe:2.3:a:frangoteam:fuxa:1.0.0:*:*:*:*:*:*:*
    cpe:2.3:a:frangoteam:fuxa:1.0.0:*:*:*:*:*:*:*
  • cpe:2.3:a:frangoteam:fuxa:1.0.1:*:*:*:*:*:*:*
    cpe:2.3:a:frangoteam:fuxa:1.0.1:*:*:*:*:*:*:*
  • cpe:2.3:a:frangoteam:fuxa:1.0.2:*:*:*:*:*:*:*
    cpe:2.3:a:frangoteam:fuxa:1.0.2:*:*:*:*:*:*:*
  • cpe:2.3:a:frangoteam:fuxa:1.0.3:*:*:*:*:*:*:*
    cpe:2.3:a:frangoteam:fuxa:1.0.3:*:*:*:*:*:*:*
  • cpe:2.3:a:frangoteam:fuxa:1.0.4:*:*:*:*:*:*:*
    cpe:2.3:a:frangoteam:fuxa:1.0.4:*:*:*:*:*:*:*
  • cpe:2.3:a:frangoteam:fuxa:1.0.5:*:*:*:*:*:*:*
    cpe:2.3:a:frangoteam:fuxa:1.0.5:*:*:*:*:*:*:*
  • cpe:2.3:a:frangoteam:fuxa:1.0.6:*:*:*:*:*:*:*
    cpe:2.3:a:frangoteam:fuxa:1.0.6:*:*:*:*:*:*:*
  • cpe:2.3:a:frangoteam:fuxa:1.0.7:*:*:*:*:*:*:*
    cpe:2.3:a:frangoteam:fuxa:1.0.7:*:*:*:*:*:*:*
  • cpe:2.3:a:frangoteam:fuxa:1.0.8:*:*:*:*:*:*:*
    cpe:2.3:a:frangoteam:fuxa:1.0.8:*:*:*:*:*:*:*
  • cpe:2.3:a:frangoteam:fuxa:1.0.9:*:*:*:*:*:*:*
    cpe:2.3:a:frangoteam:fuxa:1.0.9:*:*:*:*:*:*:*
  • cpe:2.3:a:frangoteam:fuxa:1.0.10:*:*:*:*:*:*:*
    cpe:2.3:a:frangoteam:fuxa:1.0.10:*:*:*:*:*:*:*
  • cpe:2.3:a:frangoteam:fuxa:1.0.11:*:*:*:*:*:*:*
    cpe:2.3:a:frangoteam:fuxa:1.0.11:*:*:*:*:*:*:*
  • cpe:2.3:a:frangoteam:fuxa:1.1.01:*:*:*:*:*:*:*
    cpe:2.3:a:frangoteam:fuxa:1.1.01:*:*:*:*:*:*:*
  • cpe:2.3:a:frangoteam:fuxa:1.1.2:*:*:*:*:*:*:*
    cpe:2.3:a:frangoteam:fuxa:1.1.2:*:*:*:*:*:*:*
  • cpe:2.3:a:frangoteam:fuxa:1.1.3:*:*:*:*:*:*:*
    cpe:2.3:a:frangoteam:fuxa:1.1.3:*:*:*:*:*:*:*
  • cpe:2.3:a:frangoteam:fuxa:1.1.4:*:*:*:*:*:*:*
    cpe:2.3:a:frangoteam:fuxa:1.1.4:*:*:*:*:*:*:*
  • cpe:2.3:a:frangoteam:fuxa:1.1.5:*:*:*:*:*:*:*
    cpe:2.3:a:frangoteam:fuxa:1.1.5:*:*:*:*:*:*:*
  • cpe:2.3:a:frangoteam:fuxa:1.1.6:*:*:*:*:*:*:*
    cpe:2.3:a:frangoteam:fuxa:1.1.6:*:*:*:*:*:*:*
  • cpe:2.3:a:frangoteam:fuxa:1.1.7:*:*:*:*:*:*:*
    cpe:2.3:a:frangoteam:fuxa:1.1.7:*:*:*:*:*:*:*
  • cpe:2.3:a:frangoteam:fuxa:1.1.8:*:*:*:*:*:*:*
    cpe:2.3:a:frangoteam:fuxa:1.1.8:*:*:*:*:*:*:*
  • cpe:2.3:a:frangoteam:fuxa:1.1.9:*:*:*:*:*:*:*
    cpe:2.3:a:frangoteam:fuxa:1.1.9:*:*:*:*:*:*:*
  • cpe:2.3:a:frangoteam:fuxa:1.1.10:*:*:*:*:*:*:*
    cpe:2.3:a:frangoteam:fuxa:1.1.10:*:*:*:*:*:*:*
  • cpe:2.3:a:frangoteam:fuxa:1.1.11:*:*:*:*:*:*:*
    cpe:2.3:a:frangoteam:fuxa:1.1.11:*:*:*:*:*:*:*
  • cpe:2.3:a:frangoteam:fuxa:1.1.12:*:*:*:*:*:*:*
    cpe:2.3:a:frangoteam:fuxa:1.1.12:*:*:*:*:*:*:*
  • cpe:2.3:a:frangoteam:fuxa:1.1.13:*:*:*:*:*:*:*
    cpe:2.3:a:frangoteam:fuxa:1.1.13:*:*:*:*:*:*:*
  • cpe:2.3:a:frangoteam:fuxa:1.1.14:*:*:*:*:*:*:*
    cpe:2.3:a:frangoteam:fuxa:1.1.14:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2026-25751: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2026-3381 – Compress::Raw::Zlib versions through 2.219 for Perl use potentially insecure versions of zlib. Compress::Raw::Zlib includes a copy of the zlib lib...
  • CVE-2026-3257 – UnQLite versions through 0.06 for Perl uses a potentially insecure version of the UnQLite library. UnQLite for Perl embeds the UnQLite library. V...
  • CVE-2026-29126 – Incorrect permission assignment (world-writable file) in /etc/udhcpc/default.script in International Data Casting (IDC) SFX2100 Satellite Receiver ...
  • CVE-2026-29125 – IDC SFX2100 Satalite Recievers set the `/etc/resolv.conf` file to be world-writable by any local user, allowing DNS resolver tampering that can red...
  • CVE-2026-29124 – Multiple SUID root-owned binaries are found in /home/monitor/terminal, /home/monitor/kore-terminal, /home/monitor/IDE-DPack/terminal-dpack, and /ho...