dbcve.org
FuxaApplication · Frangoteam

CVE-2025-69985

CRITICAL · 9.8 CVSS v3.1 Published 2026-02-24
Fix available
A fix is available. Upgrade to after 1.2.8 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The FUXA jwt-helper.js middleware incorrectly trusts the HTTP Referer header to determine if requests are internal, allowing attackers to spoof this header to match the server's hostname and bypass JWT authentication entirely. This grants unauthenticated access to the /api/runscript endpoint, enabling arbitrary Node.js code execution on the server.

MitigationUpgrade to FUXA version 1.2.9 or later which implements proper JWT validation without relying on the Referer header; alternatively, add server-side validation that rejects requests with spoofed Referer headers and enforce stricter authentication on the runscript endpoint.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
FuxaApplication
Affected:<= 1.2.8

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify FUXA version
    Locate the FUXA installation and check the version number (typically visible in the application UI, package.json, or server startup logs). Compare your version against the affected range: <= 1.2.8
    Affected if The installed FUXA version is 1.2.8 or lower
  2. Locate jwt-helper.js middleware
    Search the FUXA server installation for the file jwt-helper.js (typically found in the server source code directory). Inspect the file contents for logic that reads the HTTP Referer header
    Affected if The jwt-helper.js file exists and contains code that uses the Referer header to determine if requests are internal or to bypass authentication checks
  3. Check Referer-based authentication bypass
    Within jwt-helper.js, identify if authentication is skipped based solely on the Referer header matching the server hostname. Look for conditional logic that trusts Referer without JWT validation
    Affected if Authentication logic conditionally trusts the Referer header without requiring valid JWT credentials
  4. Verify /api/runscript endpoint exposure
    Check if the /api/runscript endpoint exists in the FUXA API routes and is accessible. This endpoint allows arbitrary Node.js code execution when authentication is bypassed
    Affected if The /api/runscript endpoint is exposed and accessible without valid JWT authentication when Referer header is spoofed

You are affected if FUXA version is 1.2.8 or lower AND the jwt-helper.js middleware contains logic that trusts the HTTP Referer header to bypass JWT authentication, allowing unauthenticated access to the /api/runscript endpoint.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 1.2.8
Interim mitigation

Upgrade to FUXA version 1.2.9 or later which implements proper JWT validation without relying on the Referer header; alternatively, add server-side validation that rejects requests with spoofed Referer headers and enforce stricter authentication on the runscript endpoint.

Recommended fix High confidence

Fuxa 1.2.9 or later

  1. 1. Identify the current Fuxa version by checking package.json or the running application
  2. 2. Back up the entire Fuxa installation directory and database before upgrading
  3. 3. Upgrade Fuxa to version 1.2.9 or later by running: npm install fuxa@latest or npm install [email protected]
  4. 4. Verify the upgrade completed successfully by checking the new version number
  5. 5. Restart the Fuxa service to apply changes
  6. 6. Test that authentication is properly enforced by attempting requests without valid JWT and without spoofed Referer header
  7. 7. Confirm the /api/runscript endpoint now requires valid authentication and cannot be accessed via Referer header spoofing
Caveat Review release notes for any configuration changes; standard upgrade risk of minor version changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Fuxa Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-69985 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-69985 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data