{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-25611 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-25611 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-25611 is a medium-severity code injection vulnerability in Fortinet Fortianalyzer, published on 7 Mar 2023. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2023-25611 and fix it if it is affected.\n\nWhat it is: CVE-2023-25611 is a medium-severity code injection vulnerability in Fortinet Fortianalyzer, published on 7 Mar 2023. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2023-25611 in the wild and no public exploit code.\n\nAffected product: Fortinet Fortianalyzer. 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-25611/ (Markdown: https://insights.sbomify.com/CVE-2023-25611/index.md)","id":"CVE-2023-25611","markdown":"https://insights.sbomify.com/CVE-2023-25611/index.md","name":"CVE-2023-25611","record":{"aliases":["GHSA-8w49-mjcx-h4jg"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Fortinet FortiAnalyzer","requires_auth":"high_privilege","summary":"A local attacker can execute unauthorized code or commands by inserting spreadsheet formulas in macro names within CSV files.","user_interaction":"required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"fortinet","cpe":[{"product":"fortianalyzer","vendor":"fortinet"}],"cvss":{"score":4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:C/C:L/I:L/A:N/E:X/RL:X/RC:X","version":"3.1"},"cwes":[{"id":"CWE-1236","name":"Improper Neutralization of Formula Elements in a CSV File"}],"description":"A improper neutralization of formula elements in a CSV file vulnerability in Fortinet FortiAnalyzer 6.4.0 - 6.4.9, 7.0.0 - 7.0.5, and 7.2.0 - 7.2.1 allows local attacker to execute unauthorized code or commands via inserting spreadsheet formulas in macro names.","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":"Code injection in FortiAnalyzer","id":"CVE-2023-25611","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"fortinet:fortianalyzer","products":["fortinet:fortianalyzer"],"type":"code_injection","year":"2023"},"n_packages":0,"n_references":1,"next":{"headline":"LDAP Injection Vulnerability in Apache Kerby","id":"CVE-2023-25613"},"packages":[],"prev":{"headline":"Memory corruption in FortiAnalyzer","id":"CVE-2023-25610"},"products":["FortiAnalyzer"],"published":"2023-03-07","related":[{"cvss_score":9.4,"headline":"Fortinet Multiple Products Authentication Bypass Using an Alternate Path or Channel","id":"CVE-2026-24858","kev_date_added":"2026-01-27","published":"2026-01-27"},{"cvss_score":9.3,"headline":"Memory corruption in FortiAnalyzer","id":"CVE-2023-25610","kev_date_added":null,"published":"2025-03-24"},{"cvss_score":8.8,"headline":"Server-side request forgery in Fortinet FortiAnalyzer, FortiManager","id":"CVE-2021-32603","kev_date_added":null,"published":"2021-08-05"},{"cvss_score":8.8,"headline":"Cross-site scripting in Fortinet FortiAnalyzer","id":"CVE-2020-12817","kev_date_added":null,"published":"2020-09-24"},{"cvss_score":8,"headline":"Auth bypass in FortiOS","id":"CVE-2024-48886","kev_date_added":null,"published":"2025-01-14"},{"cvss_score":8,"headline":"Cross-site scripting in Fortinet FortiAnalyzer, FortiManager","id":"CVE-2022-39950","kev_date_added":null,"published":"2022-11-02"},{"cvss_score":7.8,"headline":"Command injection in Fortinet FortiManager, FortiAnalyzer, FortiPortal","id":"CVE-2021-26104","kev_date_added":null,"published":"2022-04-06"}],"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":"partial"},"state":"PUBLISHED","updated":"2024-10-22","vendors":["Fortinet"]},"summary":"A local attacker can execute unauthorized code or commands by inserting spreadsheet formulas in macro names within CSV files.","url":"https://insights.sbomify.com/CVE-2023-25611/"}