CVE-2025-69983: FUXA · Code Injection
Affects FUXASource CVE Database V5
Not known to be exploited · CVSS 8.2 High.
Data as of 26 Oct 2026, 09:16 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 41% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 3 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubfrangoteam/FUXApkg:github/frangoteam/FUXAOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
To mitigate CVE-2025-69983, European organizations should implement the following specific measures: 1) Immediately restrict or disable the project import functionality in FUXA until a secure patch or update is available. 2) If import functionality is essential, enforce strict validation and sanitization of all imported project files, particularly scripts, to prevent execution of arbitrary commands. 3) Deploy application-level sandboxing or containerization to isolate script execution environments, minimizing potential system impact. 4) Monitor network and application logs for unusual activity related to project imports or script execution. 5) Limit network exposure of FUXA instances by placing them behind firewalls and VPNs, restricting access to trusted users only. 6) Conduct regular security audits and penetration testing focused on input validation and code execution paths. 7) Engage with the FUXA vendor or community to obtain patches or updates addressing this vulnerability as soon as they become available. 8) Educate administrators and users about the risks of importing untrusted project files and enforce strict access controls. These targeted actions go beyond generic advice by focusing on the specific attack vector and operational context of FUXA deployments.
Description
FUXA v1.2.7 allows Remote Code Execution (RCE) via the project import functionality. The application does not properly sanitize or sandbox user-supplied scripts within imported project files. An attacker can upload a malicious project containing system commands, leading to full system compromise.