# CVE-2023-31718: FUXA local file inclusion vulnerability

> An attacker can read arbitrary local files via the /api/download endpoint in FUXA, potentially exposing sensitive system data.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Sep 2023
- **Updated:** 24 Sep 2024
- **Also known as:** GHSA-wwfj-h843-3hrq

## What is CVE-2023-31718?

CVE-2023-31718 is a high-severity path traversal vulnerability in n/a, published on 21 Sep 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

FUXA <= 1.1.12 is vulnerable to Local via Inclusion via /api/download.

Weakness: CWE-98 (Improper Control of Filename for Include/Require Statement in PHP Program)

## Which versions are affected by CVE-2023-31718?

2 open source packages ship an affected version, including fuxa-server. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `fuxa-server` | npm | All versions to 1.1.12 | None |
| `fuxa-server` | npm | All versions to 1.1.12 | None |

Products: Frangoteam Fuxa.

## How do I fix CVE-2023-31718?

No fix has been published for CVE-2023-31718 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-31718 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-31718 exists.

Public exploit code:

- https://github.com/MateusTesser/CVE-2023-31718 (github_poc): https://github.com/MateusTesser/CVE-2023-31718

## Other vulnerabilities in n/a

- [CVE-2026-25893](https://insights.sbomify.com/CVE-2026-25893/): FUXA Unauthenticated Remote Code Execution via Admin JWT Minting (critical 10.0)
- [CVE-2025-69985](https://insights.sbomify.com/CVE-2025-69985/): FUXA has JWT Authentication Bypass via HTTP Referer header spoofing (critical 9.8)
- [CVE-2025-69971](https://insights.sbomify.com/CVE-2025-69971/): FUXA has a hardcoded fallback JWT signing secret (critical 9.8)
- [CVE-2023-31719](https://insights.sbomify.com/CVE-2023-31719/): FUXA SQL Injection vulnerability (critical 9.8)
- [CVE-2023-33831](https://insights.sbomify.com/CVE-2023-33831/): A remote command execution (RCE) vulnerability in the /api/runscript endpoint of FUXA (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-31718 and fix it if it is affected.

What it is: CVE-2023-31718 is a high-severity path traversal vulnerability in n/a, published on 21 Sep 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-31718 exists.

Affected packages and fixed versions:
- fuxa-server (npm): affected all versions up to 1.1.12; no fix listed
- fuxa-server (npm): affected all versions up to 1.1.12; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-31718/ (Markdown: https://insights.sbomify.com/CVE-2023-31718/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-31718
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-31718
- OSV: https://osv.dev/vulnerability/CVE-2023-31718

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-31718/
Summaries are generated and may contain mistakes; the official description above is the record.