CVE-2025-69971 — FUXA Hard-coded JWT Signing Key Authentication Bypass

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

1. Identify exposed assets running the affected vendor/product/version combinations (Frangoteam Fuxa).
2. The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
3. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
4. Search available logs for exploit probes matching the vulnerability class (authentication), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-798 · Use of Hard-coded Credentials

Other CVEs with this weakness →

Public exploits, PoCs and detection templates

Public code that demonstrates or tests the flaw raises the odds of mass exploitation — and Nuclei templates help find vulnerable assets in your environment.

Warning: public PoCs are sometimes disguised malware. Use them only for authorized testing in an isolated environment. This portal does not host exploit code — it only points to the sources.

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 2.23%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

• Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
• Review authentication logs: logins without MFA, anomalous sessions and recently created accounts.

Analysis and videos

CVE-2025-69971: FUXA Hard-coded JWT Signing Key Authentication Bypass
CVE-2025-69971 affects FUXA v1.2.7, where the JWT helper in server/api/jwt-helper.js signs and verifies tokens with a hard-coded secret, classified as CWE-798. According to the record, a remote attacker could forge administrator tokens and gain full administrative access. NVD rates it Critical with CVSS 3.1 score 9.8, and no confirmed exploitation appears in the sources consulted.

Timeline

What happened to this CVE, newest first.

• 2026
• SSVC assessment updated
  Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
• Record published
  Oct 13, 2026
• CVSS changed · 9.8
  Oct 13, 2026 · NIST National Vulnerability Database
• Source status changed · → Modified
  Oct 13, 2026 · NIST National Vulnerability Database
• Record created in this database
  Oct 13, 2026 · NIST National Vulnerability Database
• CVE published
  Feb 3, 2026 · mitre

Source activity

Repeated readings are counted rather than listed.

• 1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

1 on the record

• github.com/frangoteam/FUXA/blob/master/server/api/jwt-helper.js
  Product, NIST National Vulnerability Database

Elsewhere on this site

Related CVEs (same products)

• High CVE-2026-43947 FUXA Vulnerable to Unauthenticated Remote Code Execution via Script Test Mode Authorization Bypass Jul 21, 2026
• High CVE-2026-43945 FUXA Vulnerable to Pre-auth RCE via Path Manipulation & Configuration Injection Jul 21, 2026
• High CVE-2026-43946 FUXA has an unauthenticated arbitrary tag value disclosure via /api/getTagValue Jul 21, 2026
• Critical CVE-2025-69985 Authentication Bypass Using an Alternate Path or Channel in Frangoteam Fuxa Feb 24, 2026
• Critical CVE-2026-25938 FUXA Unauthenticated Remote Code Execution in Node-RED Integration Feb 9, 2026
• High CVE-2026-25951 FUXA has a Path Traversal Sanitization Bypass Feb 9, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

• No fixed version, patch or mitigation documented.
• No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
• No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
• No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2025-69971 is "FUXA Hard-coded JWT Signing Key Authentication Bypass", rated Critical. It affects Fuxa (Frangoteam); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 9.8 describes technical severity. EPSS 2.23% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.