Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2025-69971: FUXA v1.2.7 contains a hard-coded credential vulnerability in server/api/jwt-helper.js

63
This week
CRITICAL 9.8REMOTEDOWNGRADE

CVE-2025-69971 is a critical-severity flaw (CVSS 9.8) affecting fuxa. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

FUXA v1.2.7 contains a hard-coded credential vulnerability in server/api/jwt-helper.js. The application uses a hard-coded secret key to sign and verify JWT Tokens. This allows remote attackers to forge valid admin tokens and bypass authentication to gain full administrative access.

Why this priority

  • Critical severity
  • CISA SSVC: automatable with total technical impact
  • Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score9.8 (Critical)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance2.2% (top 17%)
CISA exploited listNo
WeaknessCWE-798
Published2026-02-03
Last modified2026-06-17
Publisher (CNA): MITRE · Vendor: frangoteam

Share: LinkedIn · X · Reddit

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

frangoteam fuxa DOWNGRADE
Affected: 1.2.7
Fixed in: no fixed release known
Safe to downgrade to: a release before 1.2.7
1. Check installed version
apt-cache policy fuxa || rpm -q fuxa || fuxa --version
2. No fixed release: DOWNGRADE to a release before 1.2.7 (Debian / Ubuntu)
apt-cache madison fuxa sudo apt install fuxa=<VERSION_BEFORE_1.2.7> sudo apt-mark hold fuxa
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list fuxa sudo dnf downgrade fuxa-<VERSION_BEFORE_1.2.7> sudo dnf versionlock add fuxa
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.

Exact fixes by distribution

A distro patch exists: prefer upgrading over downgrading.
npm · @frangoteam/fuxa · FIXED · 1.3.0 · vulnerable: <= 1.2.11 · source
npm install @frangoteam/fuxa@">=1.3.0" npm ls @frangoteam/fuxa
Fedora 46 · proftpd · FIXED · 1.3.9e-2.fc46 · FEDORA-2026-fcb0a25c2f · source
sudo dnf upgrade --advisory=FEDORA-2026-fcb0a25c2f

Public exploits and detection

Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2025-69971?

fuxa: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2025-69971 being exploited?

CVE-2025-69971 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2025-69971 affect?

CVE-2025-69971 affects fuxa. Severity is critical (CVSS 9.8). FUXA v1.2.7 contains a hard-coded credential vulnerability in server/api/jwt-helper.js. The application uses a hard-coded secret key to sign and verify JWT Tokens. This allows remote attackers to forge valid admin tokens and bypass authenti

How urgent is CVE-2025-69971?

Priority 63/100. Critical severity; CISA SSVC: automatable with total technical impact; Remotely exploitable, no login, no user action

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.