Raw vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XSummary
CVE-2026-25951 is a high-severity Path Traversal (CWE-22) vulnerability in Frangoteam Fuxa. Its CVSS base score is 8.6 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 34% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and SI-10 (Information Input Validation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-25951 is a directory traversal vulnerability in FUXA, an open-source web-based Process Visualization (SCADA/HMI/Dashboard) software. In versions prior to 1.2.11, a flaw in the path sanitization logic permits bypassing of directory traversal protections through nested traversal sequences, such as ....//. This allows an attacker to write arbitrary files to the server filesystem, including sensitive directories like runtime/scripts, ultimately enabling remote code execution (RCE) upon server reload of the malicious scripts. The vulnerability is associated with CWEs-22 (Path Traversal), CWE-23 (Relative Path Traversal), and CWE-184 (Incomplete List of Disallowed Inputs) and carries a CVSS v3.1 base score of 7.2 (AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H).
An authenticated attacker possessing administrative privileges can exploit this issue over the network with low complexity and no user interaction required. By crafting requests with nested traversal payloads, the attacker bypasses sanitization to upload malicious files into executable directories. When FUXA reloads scripts during runtime, the injected code executes with the privileges of the server process, potentially granting full control over the host system, including high confidentiality, integrity, and availability impacts.
The vulnerability is addressed in FUXA version 1.2.11, where the path sanitization logic was hardened to properly handle nested traversal attempts, as detailed in the project's GitHub security advisory (GHSA-68m5-5w2h-h837), release notes for v1.2.11, and the fixing commit (f7a9f04b2ab97ab5421e4ec4e711c51e9f4b65c8). Security practitioners should upgrade to 1.2.11 or later and review access controls to limit administrative privileges in SCADA/HMI deployments.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-6245
Vulnerability Data
FUXA is a web-based Process Visualization (SCADA/HMI/Dashboard) software. Prior to 1.2.11, there is a flaw in the path sanitization logic allows an authenticated attacker with administrative privileges to bypass directory traversal protections. By using nested traversal sequences (e.g., ....//), an…
more
attacker can write arbitrary files to the server filesystem, including sensitive directories like runtime/scripts. This leads to Remote Code Execution (RCE) when the server reloads the malicious scripts. This vulnerability is fixed in 1.2.11.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 2 hardening rules · 1 OS baseline
V3.5.2V4.4.2V16.2.5V5.3.2
Mitigating Controls (NIST 800-53 r5) AI
Enforces the intended directory access authorizations that path traversal would otherwise bypass.
Input validation directly neutralizes special path elements before pathname construction occurs.
Information-flow rules can be configured to reject traversals that would move data outside an approved directory boundary.
Least privilege reduces the impact of any unauthorized file access obtained via traversal.
Secure-engineering principles require safe pathname construction and input neutralization before any file operation.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require input validation and path sanitization that prevent relative traversal.
Patching/maintenance can remediate known path-traversal flaws in deployed software (partial prevention of exploitability) but does nothing to stop the coding defect from being introduced in the first place.
PR.AA-05 defines and reviews access policies but does not address code-level pathname neutralization, so neither direction prevents CWE-22.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development catches path traversal via static/dynamic analysis.
Secure SDLC mandates input validation and path sanitization that directly prevent path traversal.
Application security requirements include rules for safe file handling and canonicalization.
Secure architecture principles require least-privilege file access and directory isolation.
Secure coding standards explicitly forbid unsafe path construction and mandate safe APIs.
Information access restriction limits which files an application may read or write.