{"answers":{"affected":"2 open source packages ship an affected version, including @frangoteam/fuxa. It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-31716 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-31716 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-31716 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."},"fix_prompt":"Check this codebase for CVE-2023-31716 and fix it if it is affected.\n\nWhat it is: CVE-2023-31716 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.\nExploitation: There is no known exploitation of CVE-2023-31716 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- @frangoteam/fuxa (npm): affected all versions up to 1.1.12; no fix listed\n- @frangoteam/fuxa (npm): affected all versions up to 1.1.12; no fix listed\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2023-31716/ (Markdown: https://insights.sbomify.com/CVE-2023-31716/index.md)","id":"CVE-2023-31716","markdown":"https://insights.sbomify.com/CVE-2023-31716/index.md","name":"CVE-2023-31716","record":{"aliases":["GHSA-45c3-c4c3-8rqg"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"FUXA SCADA","requires_auth":"none","summary":"An attacker can read arbitrary local files via a Local File Inclusion vulnerability in the FUXA SCADA web application.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"fuxa","vendor":"frangoteam"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-98","name":"Improper Control of Filename for Include/Require Statement in PHP Program"}],"description":"FUXA \u003c= 1.1.12 has a Local File Inclusion vulnerability via file=fuxa.log","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":"2023-09-21","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2023-09-21T00:24:25Z","kind":"github_poc","ref":"https://github.com/MateusTesser/CVE-2023-31716","stars":0,"title":null}],"tier":"poc_unverified"},"has_fix":false,"headline":"FUXA vulnerable to Local File Inclusion","id":"CVE-2023-31716","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"path_traversal","year":"2023"},"n_packages":2,"n_references":2,"next":{"headline":"FUXA SQL Injection vulnerability","id":"CVE-2023-31717"},"packages":[{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["1.1.12"],"package":"@frangoteam/fuxa","purl":null,"source":"GHSA-45c3-c4c3-8rqg"},{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["1.1.12"],"package":"@frangoteam/fuxa","purl":"pkg:npm/%40frangoteam/fuxa","source":"GHSA-45c3-c4c3-8rqg"}],"prev":{"headline":"SQL injection in n/a","id":"CVE-2023-31714"},"products":["n/a"],"published":"2023-09-21","related":[{"cvss_score":10,"headline":"FUXA Unauthenticated Remote Code Execution via Admin JWT Minting","id":"CVE-2026-25893","kev_date_added":null,"published":"2026-02-09"},{"cvss_score":9.8,"headline":"FUXA has JWT Authentication Bypass via HTTP Referer header spoofing","id":"CVE-2025-69985","kev_date_added":null,"published":"2026-02-24"},{"cvss_score":9.8,"headline":"FUXA has a hardcoded fallback JWT signing secret","id":"CVE-2025-69971","kev_date_added":null,"published":"2026-02-03"},{"cvss_score":9.8,"headline":"FUXA SQL Injection vulnerability","id":"CVE-2023-31719","kev_date_added":null,"published":"2023-09-21"},{"cvss_score":9.8,"headline":"A remote command execution (RCE) vulnerability in the /api/runscript endpoint of FUXA","id":"CVE-2023-33831","kev_date_added":null,"published":"2023-09-18"},{"cvss_score":9.5,"headline":"FUXA Unauthenticated Remote Code Execution via Hardcoded JWT Secret in Default Configuration","id":"CVE-2026-25894","kev_date_added":null,"published":"2026-02-09"},{"cvss_score":9.5,"headline":"FUXA Unauthenticated Remote Code Execution via Arbitrary File Write in Upload API","id":"CVE-2026-25895","kev_date_added":null,"published":"2026-02-09"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-09-24","vendors":["n/a"]},"summary":"An attacker can read arbitrary local files via a Local File Inclusion vulnerability in the FUXA SCADA web application.","url":"https://insights.sbomify.com/CVE-2023-31716/"}