CVE-2023-31716
Frangoteam Fuxa ≤ 1.1.12
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NSummary
CVE-2023-31716 is a high-severity PHP Remote File Inclusion (CWE-98) vulnerability in Frangoteam Fuxa. Its CVSS base score is 7.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 34% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
FUXA versions 1.1.12 and earlier are affected by a local file inclusion vulnerability that can be triggered via the file parameter, for example by supplying fuxa.log. The issue is tracked as CVE-2023-31716 and carries a CVSS 3.1 base score of 7.5, reflecting network attack vector, low complexity, and no required privileges or user interaction, with high impact limited to confidentiality.
An unauthenticated remote attacker can exploit the flaw to read arbitrary local files on the server, directly exposing sensitive data such as logs or configuration contents. The weakness maps to CWE-98, indicating improper control of filenames used in include or require operations.
Public references consist of a proof-of-concept repository and the upstream FUXA project page; neither reference supplies patch details or mitigation steps. The EPSS score stands at 0.3711 with an identical recorded peak, indicating no material post-disclosure rise.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-2413
Vulnerability Data
FUXA <= 1.1.12 has a Local File Inclusion vulnerability via file=fuxa.log
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices such as input validation and allow-listing of include paths directly prevent the weakness.
Hardened runtime configuration (e.g., allow_url_include=off) directly blocks RFI even if code is flawed.
Execution restrictions can prevent the remote payload from running, while eliminating the weakness reduces the need for such controls.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can detect RFI but does not prevent the weakness by itself.
Secure development lifecycle mandates input validation and safe include/require patterns that directly prevent remote file inclusion.
Application security requirements explicitly call for controls against injection and unsafe file operations.
Secure architecture principles reduce attack surface but do not specifically address dynamic file inclusion.
Secure coding standards directly require whitelisting and sanitization of filenames used in include/require statements.
Information access restriction limits what files can be read but does not address dynamic inclusion logic.