{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-47541 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-47541 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-47541 is a medium-severity path traversal vulnerability in Fortinet Fortisandbox, published on 9 Apr 2024. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-47541 and fix it if it is affected.\n\nWhat it is: CVE-2023-47541 is a medium-severity path traversal vulnerability in Fortinet Fortisandbox, published on 9 Apr 2024. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-47541 in the wild and no public exploit code.\n\nAffected product: Fortinet Fortisandbox. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-47541/ (Markdown: https://insights.sbomify.com/CVE-2023-47541/index.md)","id":"CVE-2023-47541","markdown":"https://insights.sbomify.com/CVE-2023-47541/index.md","name":"CVE-2023-47541","record":{"aliases":["GHSA-cfhh-2gpx-32wx"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Fortinet FortiSandbox","requires_auth":"high_privilege","summary":"Attackers can execute unauthorized code or commands via CLI due to a path traversal vulnerability in FortiSandbox.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"fortinet","cpe":[{"product":"fortisandbox","vendor":"fortinet"}],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H/E:F/RL:X/RC:C","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"An improper limitation of a pathname to a restricted directory ('path traversal') vulnerability in Fortinet FortiSandbox 4.4.0 through 4.4.2, FortiSandbox 4.2.1 through 4.2.6, FortiSandbox 4.0 all versions, FortiSandbox 3.2 all versions, FortiSandbox 3.1 all versions, FortiSandbox 3.0 all versions, FortiSandbox 2.5 all versions, FortiSandbox 2.4 all versions, FortiSandbox 2.3 all versions, FortiSandbox 2.2 all versions, FortiSandbox 2.1 all versions, FortiSandbox 2.0 all versions allows attacker to execute unauthorized code or commands via CLI.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Path traversal in FortiSandbox","id":"CVE-2023-47541","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"fortinet:fortisandbox","products":["fortinet:fortisandbox"],"type":"path_traversal","year":"2023"},"n_packages":0,"n_references":1,"next":{"headline":"Code injection in FortiManager","id":"CVE-2023-47542"},"packages":[],"prev":{"headline":"Command injection in FortiSandbox","id":"CVE-2023-47540"},"products":["FortiSandbox"],"published":"2024-04-09","related":[{"cvss_score":9.1,"headline":"Fortinet FortiSandbox OS Command Injection","id":"CVE-2026-25089","kev_date_added":"2026-07-16","published":"2026-06-09"},{"cvss_score":9.1,"headline":"Fortinet FortiSandbox OS Command Injection","id":"CVE-2026-39808","kev_date_added":"2026-07-16","published":"2026-04-14"},{"cvss_score":9.1,"headline":"Missing authorization in FortiSandbox","id":"CVE-2026-26083","kev_date_added":null,"published":"2026-05-12"},{"cvss_score":9.1,"headline":"Path traversal in FortiSandbox","id":"CVE-2026-39813","kev_date_added":null,"published":"2026-04-14"},{"cvss_score":8.8,"headline":"SQL injection in Fortinet FortiSandbox","id":"CVE-2020-29011","kev_date_added":null,"published":"2021-08-04"},{"cvss_score":8.8,"headline":"Command injection in Fortinet FortiSandbox","id":"CVE-2021-26097","kev_date_added":null,"published":"2021-08-04"},{"cvss_score":8.6,"headline":"Command injection in FortiSandbox","id":"CVE-2024-52961","kev_date_added":null,"published":"2025-03-11"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-01-14","vendors":["Fortinet"]},"summary":"Attackers can execute unauthorized code or commands via CLI due to a path traversal vulnerability in FortiSandbox.","url":"https://insights.sbomify.com/CVE-2023-47541/"}