FUXA 1.2.8 and prior contains an Authentication Bypass vulnerability leading to Remote Code Execution (RCE). The vulnerability exists in the server/api/jwt-helper.js middleware, which improperly trusts the HTTP "Referer" header to validate internal requests. A remote unauthenticated attacker can bypass JWT authentication by spoofing the Referer header to match the server's host. Successful exploitation allows the attacker to access the protected /api/runscript endpoint and execute arbitrary Node.js code on the server.
CVE-2025-69985
CRITICALPre-NVD 9.89.8—Trending — 3 sources updated this weekElevated
EchelonGraph scoreMEDIUM confidence
Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-02-24. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 9.8; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, ghsa
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 6%CVSS: 9.8Exploit: Elevated riskExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.8
- EG Score
- 9.8(medium)
- EG Risk
- 59(Attend)EG Risk 59/100SSVC: Attend
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity98% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Remediate soon — notable exploitation risk. - EPSS PROB
- 6%
- EPSS %ILE
- 92%
- KEV
- Not listed
Published
February 24, 2026
Last Modified
June 17, 2026
Advisory Details (2)
Auto-updated Jul 27, 2026🔬 Proof of concept available. No patch confirmed yet.
generic🟡 PoC Available
FUXA 1.2.8 Authentication Bypass & RCE PoC · GitHub
https://gist.github.com/lihy10/8cb2dd65ebf1385f12a7e00e25a50d40generic
FUXA/server/api/jwt-helper.js at master · frangoteam/FUXA · GitHub
https://github.com/frangoteam/FUXA/blob/master/server/api/jwt-helper.jsPatch Availability(1)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| npm | @frangoteam/fuxa | — | ghsa |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 3× in last 7d / 3× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-27 14:13 UTCEPSS rescore
- 2026-07-27 12:55 UTCEG score recompute
- 2026-07-27 12:55 UTCGHSA enrichment
Publicly available exploits
(2 references)Working exploit code is in the public domain (1 GitHub PoC) (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.
- Exploit-DBEDB-52544First seen Apr 30, 2026
FUXA 1.2.8 - Authentication Bypass + RCE Exploit
Open source ↗ - GitHub PoCjoshuavanderpoll/CVE-2025-69985First seen Feb 25, 2026
CVE-2025-69985: FUXA ≤1.2.8 Auth Bypass + RCE via /api/runscript
Open source ↗
Frequently asked(5)
What is CVE-2025-69985?
CVE-2025-69985 is a critical vulnerability published on February 24, 2026. FUXA 1.2.8 and prior contains an Authentication Bypass vulnerability leading to Remote Code Execution (RCE). The vulnerability exists in the server/api/jwt-helper.js middleware, which improperly trusts the HTTP "Referer" header to validate internal requests. A remote unauthenticated attacker can…
When was CVE-2025-69985 disclosed?
CVE-2025-69985 was first published in the National Vulnerability Database on February 24, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-69985 actively exploited?
CVE-2025-69985 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 6% probability of exploitation in the next 30 days, which ranks it in the top 7.9% of all scored CVEs.
What is the CVSS score of CVE-2025-69985?
CVE-2025-69985 has a CVSS v3.1 base score of 9.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2025-69985?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-69985, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2025-69985
Is Your Infrastructure Affected by CVE-2025-69985?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.