Skip to content
Fencer Intel
high 7.5

CVE-2023-31718 json

FUXA local file inclusion vulnerability

published 3y ago modified 4mo ago also GHSA-wwfj-h843-3hrq , EUVD-2023-2610

cvss
7.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.7%
EPSS 1.7% chance of exploitation in 30 days, percentile 78%
public exploits
0
none known

Summary

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

Is CVE-2023-31718 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
Proof of concept is public
Automatable
yes
Technical impact
partial
Assessed
2y ago

Exploit prediction

1.73% chance of exploitation in the next 30 days, higher than 78% of all scored CVEs (FIRST EPSS, 2026-11-15).

Exploits and checks

  • youtu.be https://youtu.be/VCQkEGntN04 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
GitHub 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
npm fuxa-server
<=1.1.12
no fix listed

Classification

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

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.