CVE-2025-69971: FUXA Server Hard-Coded Credential Vulnerability

fuxa-server Updated 04 Feb 2026

Summary

03/02/2026
No i
High
8.1

CVE-2025-69971: FUXA contains a hard-coded credential vulnerability. Affects fuxa-server versions < 1.2.7. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

FUXA is an open-source server application designed for building and managing APIs with a focus on security and ease of use. The package, specifically fuxa-server, is widely utilized in Node.js environments for its ability to handle JSON Web Tokens (JWT) for authentication. However, version 1.2.7 of FUXA contains a critical vulnerability due to the use of hard-coded credentials, which compromises its security framework.

Vulnerability Detail

The vulnerability in FUXA arises from a hard-coded secret key located in the server/api/jwt-helper.js file. This key is used to sign and verify JWT tokens, which are essential for user authentication. As a result, remote attackers can exploit this vulnerability to forge valid admin tokens, allowing them to bypass authentication mechanisms and gain unauthorized administrative access to the application. The implications of this vulnerability are severe, as it can lead to complete control over the server, data breaches, and potential exploitation of sensitive user information.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As a temporary workaround, you can replace the hard-coded secret key in the jwt-helper.js file with an environment variable. This can be done by modifying the code as follows:

const secretKey = process.env.JWT_SECRET || 'your-default-secret';

Make sure to set the JWT_SECRET environment variable in your server configuration to a secure, randomly generated string.

Conclusion

The hard-coded credential vulnerability in FUXA version 1.2.7 poses a significant risk to applications using this package. It is essential to update to a patched version or implement the suggested workaround to secure your application against potential attacks. Regular monitoring for vulnerabilities using tools like Vulert can help maintain the security of your software.

See every vulnerability recorded for fuxa-server →

Share this vulnerability

FAQ

The vulnerability has a CVSS score of 8.1, indicating a high severity level that requires immediate attention.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any sign-up.

If exploited, this vulnerability can allow attackers to gain full administrative access to the server, leading to data breaches and unauthorized actions.

Yes, updating to the latest version of the fuxa-server package will resolve the vulnerability. Always check the release notes for any changes.

Implement the workaround by using an environment variable for the secret key to mitigate the risk until you can update the package.

Related vulnerabilities

Recent vulnerabilities recorded for fuxa-server.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback