dbcve.org
FuxaApplication · Frangoteam

CVE-2025-69983

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 allows Remote Code Execution (RCE) via the project import functionality. The application does not properly sanitize or sandbox user-supplied scripts within imported project files. An attacker can upload a malicious project containing system commands, leading to full system compromise.

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 contains a critical RCE vulnerability in its project import functionality. The application fails to sanitize or sandbox user-supplied scripts embedded in imported project files, allowing attackers to execute arbitrary system commands and achieve full system compromise by uploading malicious project files.

MitigationDisable or restrict the project import functionality until a security patch is available. Implement strict input validation, sanitization, and sandboxing for all scripts and commands within imported project files.

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 installed FUXA version
    Check the application's version information, typically found in the UI footer, package.json file, or by querying the application's API endpoint for version details
    Affected if The installed version is exactly 1.2.7
  2. Verify project import feature accessibility
    Check if the project import functionality is enabled and accessible in the application. This may be visible in the UI as an import option or accessible via API endpoints such as /api/projects/import or similar import-related routes
    Affected if The project import feature is enabled and accessible to users
  3. Inspect project file handling configuration
    Review FUXA configuration files (such as settings.json or similar config files in the application directory) for any settings related to project import, script execution, or sandbox configuration
    Affected if No script sandboxing or validation settings are found or configured for imported projects
  4. Check for existing imported project files
    Examine the application's data or projects directory for any recently imported project files that may contain embedded scripts or commands
    Affected if Imported project files exist in the system and can contain unsandboxed scripts

You are affected if running FUXA version 1.2.7 AND the project import feature is accessible, as the vulnerability allows arbitrary code execution through malicious imported project 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

Disable or restrict the project import functionality until a security patch is available. Implement strict input validation, sanitization, and sandboxing for all scripts and commands within imported project files.

Recommended fix Moderate confidence

Latest stable release newer than v1.2.7 (check GitHub releases for specific version)

  1. 1. Identify the current FUXA installation version by checking the application interface or package configuration
  2. 2. Navigate to the official FUXA GitHub repository releases page at github.com/frangoteam/FUXA/releases
  3. 3. Identify the latest stable release version that is newer than v1.2.7
  4. 4. Review the release notes for the fixed version to confirm the RCE vulnerability (CVE-2025-69983) is addressed
  5. 5. Backup the current FUXA application data, configuration, and any existing projects
  6. 6. Stop the FUXA service or application
  7. 7. Upgrade FUXA to the fixed version following the official upgrade documentation
  8. 8. Verify the upgrade was successful by checking the application version
Caveat Review release notes for any breaking changes between v1.2.7 and the target upgrade version, particularly around project import functionality

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

Fix this in Fuxa Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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