# CVE-2025-69985: FUXA has JWT Authentication Bypass via HTTP Referer header spoofing

> Remote attackers can bypass authentication by spoofing the Referer header to execute arbitrary code on FUXA servers.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Feb 2026
- **Updated:** 25 Feb 2026
- **Also known as:** GHSA-4r4r-4jp4-wwf9

## What is CVE-2025-69985?

CVE-2025-69985 is a critical authentication bypass vulnerability in n/a, published on 24 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-288 (Authentication Bypass Using an Alternate Path or Channel)

## Which versions are affected by CVE-2025-69985?

2 open source packages ship an affected version, including @frangoteam/fuxa. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@frangoteam/fuxa` | npm | All versions to 1.2.8 | None |
| `@frangoteam/fuxa` | npm | All versions to 1.2.8 | None |

Products: Frangoteam Fuxa.

## How do I fix CVE-2025-69985?

No fix has been published for CVE-2025-69985 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-69985 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-69985 exists.

Public exploit code:

- CVE-2025-69985: FUXA ≤1.2.8 Auth Bypass + RCE via /api/runscript (github_poc): https://github.com/joshuavanderpoll/CVE-2025-69985
- FUXA 1.2.8 - Authentication Bypass + RCE Exploit (exploitdb)
- https://github.com/kaleth4/CVE-2025-69985 (github_poc): https://github.com/kaleth4/CVE-2025-69985

## Other vulnerabilities in n/a

- [CVE-2026-25893](https://insights.sbomify.com/CVE-2026-25893/): FUXA Unauthenticated Remote Code Execution via Admin JWT Minting (critical 10.0)
- [CVE-2025-69971](https://insights.sbomify.com/CVE-2025-69971/): FUXA has a hardcoded fallback JWT signing secret (critical 9.8)
- [CVE-2023-31719](https://insights.sbomify.com/CVE-2023-31719/): FUXA SQL Injection vulnerability (critical 9.8)
- [CVE-2023-33831](https://insights.sbomify.com/CVE-2023-33831/): A remote command execution (RCE) vulnerability in the /api/runscript endpoint of FUXA (critical 9.8)
- [CVE-2026-25894](https://insights.sbomify.com/CVE-2026-25894/): FUXA Unauthenticated Remote Code Execution via Hardcoded JWT Secret in Default Configuration (critical 9.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-69985 and fix it if it is affected.

What it is: CVE-2025-69985 is a critical authentication bypass vulnerability in n/a, published on 24 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-69985 exists.

Affected packages and fixed versions:
- @frangoteam/fuxa (npm): affected all versions up to 1.2.8; no fix listed
- @frangoteam/fuxa (npm): affected all versions up to 1.2.8; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-69985/ (Markdown: https://insights.sbomify.com/CVE-2025-69985/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-69985
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-69985
- OSV: https://osv.dev/vulnerability/CVE-2025-69985

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-69985/
Summaries are generated and may contain mistakes; the official description above is the record.