Skip to content

FUXA has a hardcoded fallback JWT signing secret

High severity GitHub Reviewed Published Mar 6, 2026 in frangoteam/FUXA • Updated Mar 7, 2026

Package

npm @frangoteam/fuxa (npm)

Affected versions

<= 1.2.11

Patched versions

1.3.0

Description

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.

References

@unocelli unocelli published to frangoteam/FUXA Mar 6, 2026
Published to the GitHub Advisory Database Mar 7, 2026
Reviewed Mar 7, 2026
Last updated Mar 7, 2026

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

EPSS score

Weaknesses

Use of Hard-coded Cryptographic Key

The product uses a hard-coded, unchangeable cryptographic key. Learn more on MITRE.

CVE ID

No known CVE

GHSA ID

GHSA-c8m8-3jcr-6rj5

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.