CVE-2025-69971Public exploitNetwork attack vector

Authentication bypass via static fallback JWT secret

Published Feb 3, 2026 · Updated Feb 3, 2026

Hard-coded cryptographic key use in frangoteam FUXA before 1.3.0 allows remote attackers to forge administrator JWTs. In server/api/jwt-helper.js, init() retains the static fallback signing secret when no secretCode is configured, and verifyToken() trusts JWT claims validated with that key. Authentication must be enabled without a custom secret; knowledge of the fallback value grants administrative access to protected project data.

CVSS severity8.1
High
EPSS probability2.04%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Hard-coded cryptographic key use in frangoteam FUXA before 1.3.0 allows remote attackers to forge administrator JWTs. In server/api/jwt-helper.js, init() retains the static fallback signing secret when no secretCode is configured, and verifyToken() trusts JWT claims validated with that key. Authentication must be enabled without a custom secret; knowledge of the fallback value grants administrative access to protected project data.

The record

CVE
CVE-2025-69971
Published
Feb 3, 2026
Updated
Feb 3, 2026
Vendor
Unknown vendor
Product
Unknown product
Classifications
CWE-321, CWE-798, T1606
Attack vector
network
Privileges
Unavailable

Timeline

How it unfolded

  1. Feb 3, 2026CVE publishedPublication date reported by the CVE source.
  2. Feb 3, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Affected buildAffected product and version details are unavailable.

What conditions does exploitation require?

Attack vectornetwork
Required privilegesUnavailable in this record.

What is affected?

Affected products and versions are unavailable in this record.

Published CVSS scores

9.8NIST NVDCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
8.1GitHub Security AdvisoryCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
9.8CISA-ADPCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
PrivilegesUnavailable
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-321Use of Hard-coded Cryptographic Key
CWE-798Use of Hard-coded Credentials
T1606Forge Web Credentials

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo