dbcve.org
FuxaApplication · Frangoteam

CVE-2025-69981

CRITICAL · 9.8 CVSS v3.1 Published 2026-02-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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 v1.2.7 contains an Unrestricted File Upload vulnerability in the `/api/upload` API endpoint. The endpoint lacks authentication mechanisms, allowing unauthenticated remote attackers to upload arbitrary files. This can be exploited to overwrite critical system files (such as the SQLite user database) to gain administrative access, or to upload malicious scripts to execute arbitrary code.

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

FUXA v1.2.7 has an unauthenticated file upload vulnerability in the `/api/upload` endpoint that allows remote attackers to upload arbitrary files without authentication. Attackers can overwrite critical system files like the SQLite user database to gain administrative access or upload malicious scripts for remote code execution.

MitigationImplement authentication and authorization checks on the `/api/upload` endpoint, add strict file type validation and whitelist filtering, and ensure uploaded files cannot overwrite critical system files or be executed from upload directories.

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.7

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
    Check the installed FUXA version (typically via package.json or version info in the application)
    Affected if The installed version is exactly 1.2.7
  2. Verify /api/upload endpoint exposure
    Send a request to the /api/upload endpoint without any authentication headers or credentials
    Affected if The endpoint accepts requests and does not return an authentication error or require login
  3. Test file upload without restrictions
    Send a POST request to /api/upload with a file (such as a test .txt or .js file) and observe if it is accepted without file type validation
    Affected if The endpoint accepts arbitrary file types without rejecting them based on an allowlist
  4. Confirm upload directory is web-accessible
    Inspect the application configuration to determine where uploaded files are stored and whether that directory is accessible via the web server
    Affected if Uploaded files are stored in a web-accessible directory and can be retrieved via HTTP
  5. Check for ability to overwrite system files
    Attempt to upload a file with a name that matches system files (such as database files) and verify if the application allows overwriting
    Affected if The application permits overwriting existing files in protected system directories

A defender is affected if running FUXA version 1.2.7 and the /api/upload endpoint is exposed without authentication, allowing unrestricted file uploads that can be accessed via the web or overwrite system files.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement authentication and authorization checks on the `/api/upload` endpoint, add strict file type validation and whitelist filtering, and ensure uploaded files cannot overwrite critical system files or be executed from upload directories.

Recommended fix Moderate confidence

Latest stable FUXA release after 1.2.7 (check GitHub releases for the patched version)

  1. 1. Back up the current FUXA installation and all configuration/data files before making any changes.
  2. 2. Visit the official FUXA GitHub repository (github.com/frangoteam/FUXA) to check for releases newer than version 1.2.7.
  3. 3. Download the latest stable release that addresses CVE-2025-69981.
  4. 4. Review the release notes or changelog to confirm the vulnerability is patched in the new version.
  5. 5. Replace the existing FUXA installation with the new version, preserving configuration files if applicable.
  6. 6. Restart the FUXA service.
  7. 7. Verify that the `/api/upload` endpoint now requires authentication or properly validates uploaded files.
  8. 8. Test that legitimate file upload functionality still works as expected.
Caveat Review release notes for any breaking changes between 1.2.7 and the target version, particularly regarding API changes or configuration file formats

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

Fix this in Fuxa Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-69981 — 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-69981 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