CVE-2025-69985: FUXA · Authentication Bypass Using an Alternate Path or Channel
Affects FUXASource CVE Database V5
Public exploit available (Exploit-DB) · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 13:47 UTC
- EPSS
- 5.9% chance of exploitation in 30 days – higher than 93% 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:H/I:H/A:HExploitation evidence
t = 0 is the CVE’s publication on cve.org
Disclosed: evidence found.
CVE published 24 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: evidence found.
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
Timeline
CVE ID reserved
by MITRE Corporation
, 46 days before disclosure
CVE published
on cve.org
, t = 0
In Threat Radar
record ingested
, the same day as disclosure
First Exploit-DB entry (opens in a new tab)
FUXA 1.2.8 - Authentication Bypass + RCE Exploit
, 65 days after disclosure
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-69985, organizations should immediately upgrade FUXA to a version where this vulnerability is patched once available. In the interim, restrict access to the /api/runscript endpoint by implementing network-level controls such as firewall rules or VPN-only access to limit exposure to trusted internal users. Disable or remove the vulnerable jwt-helper.js middleware if feasible or replace the Referer header validation with robust JWT token verification that does not rely on easily spoofed HTTP headers. Employ Web Application Firewalls (WAFs) with custom rules to detect and block suspicious Referer header spoofing attempts targeting the API. Conduct thorough code reviews and penetration testing to identify similar insecure trust assumptions in other parts of the application. Monitor logs for unusual API access patterns and unauthorized code execution attempts. Finally, implement strict Node.js runtime security controls such as sandboxing and least privilege execution to limit the impact of potential code execution vulnerabilities.
Description
FUXA 1.2.8 and prior contains an Authentication Bypass vulnerability leading to Remote Code Execution (RCE). The vulnerability exists in the server/api/jwt-helper.js middleware, which improperly trusts the HTTP "Referer" header to validate internal requests. A remote unauthenticated attacker can bypass JWT authentication by spoofing the Referer header to match the server's host. Successful exploitation allows the attacker to access the protected /api/runscript endpoint and execute arbitrary Node.js code on the server.