Quick answers
- Is CVE-2023-31716 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2023-31716 being exploited in the wild.
- How severe is CVE-2023-31716?
- Low severity, with a CVSS score of 3.1, published 22 September 2023.
- Which products and versions are affected?
- Frangoteam FUXA <=1.1.12; @frangoteam/fuxa (npm) SEMVER:introduced=0,last_affected=1.1.12.
- Is there a fix for CVE-2023-31716?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2023-31716 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2023-31716?
- Check whether you run Frangoteam FUXA or @frangoteam/fuxa (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
FUXA versions up to and including 1.1.12 contain a local file inclusion (LFI) vulnerability in the file parameter handling, classified under CWE-98 (Improper Control of Filename for Include/Require Statement in PHP Program). The vulnerability allows attackers to access arbitrary files on the server filesystem, including the fuxa.log file, by directly manipulating the file parameter in requests. The attack is network-accessible, requires no authentication or user interaction, and allows full confidentiality compromise through arbitrary file disclosure. No patch information is available in the advisory text, though users should upgrade to a version newer than 1.1.12 if available.
Affected products
- frangoteam FUXA <=1.1.12
Identifiers
- CVE-2023-31716
- GHSA-45c3-c4c3-8rqg
Timeline
- 2023-09-22: disclosed