Skip to main content
VulnerabilityPublished Updated

CVE-2025-69971: FUXA v1.2.7 contains a hard-coded credential

Affects FUXASource CVE Database V5

0

Not known to be exploited · public detection template (Nuclei) · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 11:42 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
2.2% chance of exploitation in 30 days – higher than 82% 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:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 3 Feb 2026

  2. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  3. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  4. Observed by OffSeq 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

ProductAffectedFixed in
GitHubfrangoteam/FUXApkg:github/frangoteam/FUXAOther threatsAffected
  • =1.2.7
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-69971, organizations should immediately audit their FUXA deployments to identify affected versions, specifically version 1.2.7. Since no official patches are currently available, temporary mitigations include disabling JWT-based authentication or restricting access to the FUXA server to trusted internal networks only. Administrators should rotate any secrets or credentials associated with FUXA and consider implementing external authentication mechanisms such as OAuth or LDAP integration to replace vulnerable JWT usage. Monitoring and logging should be enhanced to detect suspicious JWT token usage or unexpected administrative actions. Network-level controls such as firewalls and VPNs should be employed to limit exposure. Organizations should maintain close contact with FUXA developers or vendors for forthcoming patches and apply them promptly once released. Additionally, conducting penetration testing and threat hunting focused on JWT forgery attempts can help identify exploitation attempts early. Finally, educating administrators about the risks of hard-coded credentials and enforcing secure coding practices will help prevent similar vulnerabilities in the future.

Description

FUXA v1.2.7 contains a hard-coded credential vulnerability in server/api/jwt-helper.js. The application uses a hard-coded secret key to sign and verify JWT Tokens. This allows remote attackers to forge valid admin tokens and bypass authentication to gain full administrative access.

References

Community reviews

Loading reviews…