CVE-2025-69971 — @frangoteam/fuxa
CRITICALCVE-2025-69971 is a critical-severity (CVSS 9.8) Hard-coded Credentials vulnerability in @frangoteam/fuxa. A fix is available for @frangoteam/fuxa — see the affected versions and patch details below.
FUXA has a hardcoded fallback JWT signing secret
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2025-69971.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2025-69971 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 388,997 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
@frangoteam/fuxanpmDescription
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @frangoteam/fuxa | all versions | 1.3.0npm install @frangoteam/fuxa@1.3.0 |
Affected Products
fuxafrangoteamDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @frangoteam/fuxa, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @frangoteam/fuxa to 1.3.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-69971 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.
How to detect CVE-2025-69971
A community-maintained Nuclei template exists for this CVE. You can scan for it directly:
nuclei -id cve-2025-69971 -u https://target- Template
- FUXA <= 1.2.7 - Hardcoded JWT Secret Authentication Bypass
- Severity
- critical
- Impact
- Remote attackers can bypass authentication and gain full administrative access.
- Remediation
- Update to the latest version that removes hard-coded credentials.
Template by ProjectDiscovery nuclei-templates (trader642), MIT licensed. View the full template. Scan only systems you are authorised to test.
Frequently Asked Questions
Is CVE-2025-69971 in your dependencies?
Find it across npm, including transitive dependencies.