CVE
CVE-2025-69971
FUXA has a hardcoded fallback JWT signing secret
FUXA used a static fallback JWT signing secret (frangoteam751) when no secretCode was configured.
If authentication was enabled without explicitly setting a custom secret, an attacker who knew the default value could forge valid JWT tokens and bypass authentication.
This issue has been addressed in version 1.3.0 by removing the static fallback and generating a secure random secret when no secretCode is provided.
Package Versions Affected
Package Version
patch Availability
No items found.
Automatically patch vulnerabilities without upgrading
Fix Without Upgrading
Detect compatible fix
Apply safe remediation
Fix with a single pull request
CVSS Version
Severity
Base Score
CVSS Version
Score Vector
C
H
U
9.8
-
3.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
C
H
U
0
-
3.1
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
C
H
U
8.1
-
3.1
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
Related Resources
No items found.
References
https://github.com/frangoteam/FUXA/security/advisories/GHSA-c8m8-3jcr-6rj5, https://nvd.nist.gov/vuln/detail/CVE-2025-69971, https://github.com/frangoteam/FUXA, https://github.com/frangoteam/FUXA/blob/master/server/api/jwt-helper.js
Basic Information
Ecosystem
