dbcve.org
FuxaApplication · Frangoteam

CVE-2023-31716

HIGH · 7.5 CVSS v3.1 Published 2023-09-22
Fix available
A fix is available. Upgrade to after 1.1.12 or later.
See remediation →
84/100
Remediation priority · High
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.1.12 has a Local File Inclusion vulnerability via file=fuxa.log

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 · moderate confidence

FUXA version 1.1.12 and earlier contains a Local File Inclusion (LFI) vulnerability via the 'file' parameter, allowing attackers to read arbitrary files on the server filesystem, including sensitive files like fuxa.log.

MitigationUpgrade to a version newer than 1.1.12 that includes the security patch, or implement strict input validation and path sanitization on the file parameter to restrict access to allowed directories only.

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

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
None
Availability
None

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

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 version displayed in the FUXA web interface (usually on the login page or in Settings > About), or inspect the package.json file in the FUXA installation directory
    Affected if The displayed version is 1.1.12 or lower
  2. Locate FUXA installation directory
    Find where FUXA is installed - common paths include /opt/fuxa, /home/fuxa, or the directory from which the application was started. Check for the presence of server.js or the package.json file
    Affected if The installation directory exists and contains FUXA files
  3. Check if web server is accessible
    Determine if the FUXA web interface port (default 1881) is listening and accessible over network. Use 'netstat -tuln | grep 1881' or curl to test connectivity
    Affected if The FUXA HTTP service is exposed and reachable
  4. Inspect application logs for LFI indicators
    Examine fuxa.log files in the FUXA installation or logs directory for unusual file parameter requests or path traversal patterns
    Affected if Log files contain suspicious requests with '../' or absolute paths in file parameters
  5. Verify file parameter endpoint exists
    Test if the file parameter endpoint is functional by sending a benign request to an accessible path (e.g., check if the server responds to file parameter queries). This typically targets /api/file or similar endpoints
    Affected if The endpoint accepts a file parameter and returns file contents

A user is affected if running FUXA version 1.1.12 or earlier with the web interface accessible, as the LFI vulnerability allows reading arbitrary files through the file parameter without authentication.

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.1.12
Interim mitigation

Upgrade to a version newer than 1.1.12 that includes the security patch, or implement strict input validation and path sanitization on the file parameter to restrict access to allowed directories only.

Recommended fix Moderate confidence

version 1.1.13 or later

  1. 1. Back up your current FUXA installation and configuration
  2. 2. Download the latest stable release from the FUXA GitHub repository (frangoteam/FUXA)
  3. 3. Stop the FUXA service
  4. 4. Replace the existing FUXA files with the new version
  5. 5. Restore your configuration from the backup if needed
  6. 6. Restart the FUXA service
  7. 7. Verify the application loads correctly and test that the file parameter is no longer vulnerable to LFI
Caveat Review release notes for any breaking changes between 1.1.12 and the target version

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

Fix this in Fuxa Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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