Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.5amended

FUXA vulnerable to Local File Inclusion

CVE-2023-31716GHSA-45c3-c4c3-8rqg

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm @frangoteam/fuxa

    Affected
    <= 1.1.12
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS
  • CVE-2023-31716: 1.40% estimated exploitation activity in the next 30 days; percentile 72.44 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

FUXA <= 1.1.12 has a Local File Inclusion vulnerability via file=fuxa.log

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-45c3-c4c3-8rqg

  2. Revision 1 · created ·

    Published from osv record GHSA-45c3-c4c3-8rqg

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2023-31716

Advisory: FUXA vulnerable to Local File Inclusion
IDs: CVE-2023-31716, GHSA-45c3-c4c3-8rqg
Record: https://patchnext.com/advisories/cve-2023-31716 (revision 2, source checked 26 Oct 2026, 12:31 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @frangoteam/fuxa: affected <= 1.1.12

## Suggested inspection (read-only)
- `npm ls @frangoteam/fuxa --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on @frangoteam/fuxa.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-45c3-c4c3-8rqg (OSV record GHSA-45c3-c4c3-8rqg lists affected ranges: npm @frangoteam/fuxa >=0 <=1.1.12)
- Verified: https://github.com/advisories/GHSA-45c3-c4c3-8rqg (GitHub-reviewed advisory GHSA-45c3-c4c3-8rqg lists affected ranges: npm @frangoteam/fuxa >=0 <=1.1.12)

Commands are suggestions: review each one before running it.

Loading voting…