{"answers":{"affected":"2 open source packages ship an affected version, including bagisto/bagisto. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-62417 exists.","fix":"Upgrade bagisto/bagisto to 2.3.8 or later.","what":"CVE-2025-62417 is a high-severity vulnerability in bagisto, published on 16 Oct 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-62417 and fix it if it is affected.\n\nWhat it is: CVE-2025-62417 is a high-severity vulnerability in bagisto, published on 16 Oct 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-62417 exists.\n\nAffected packages and fixed versions:\n- bagisto/bagisto (Packagist): affected all versions; fixed in 2.3.8\n- bagisto/bagisto (Packagist): affected all versions; fixed in 2.3.8\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-2025-62417/ (Markdown: https://insights.sbomify.com/CVE-2025-62417/index.md)","id":"CVE-2025-62417","markdown":"https://insights.sbomify.com/CVE-2025-62417/index.md","name":"CVE-2025-62417","record":{"aliases":["GHSA-jqrp-58fv-w8cq"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution","data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Laravel eCommerce platform","requires_auth":"none","summary":"Attackers can inject malicious formulas into product data, leading to code execution or data exfiltration when victims open exported CSV files in spreadsheet software.","user_interaction":"required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"bagisto","vendor":"webkul"}],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P","version":"4.0"},"cwes":[{"id":"CWE-1236","name":"Improper Neutralization of Formula Elements in a CSV File"}],"description":"Bagisto is an open source laravel eCommerce platform. When product data that begins with a spreadsheet formula character (for example =, +, -, or @) is accepted and later exported or saved into a CSV and opened in spreadsheet software, the spreadsheet will interpret that cell as a formula. This allows an attacker to supply a CSV field (e.g., product name) that contains a formula which may be evaluated by a victim’s spreadsheet application — potentially leading to data exfiltration and remote command execution (via older Excel exploits / OLE/cmd constructs or Excel macros). This vulnerability is fixed in 2.3.8.","ecosystems":["Packagist"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"bagisto - CSV Formula Injection in Create New Product","id":"CVE-2025-62417","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"other","year":"2025"},"n_packages":2,"n_references":1,"next":{"headline":"bagisto - Cross Site Scripting (XSS) in TinyMCE Image Upload (SVG)","id":"CVE-2025-62418"},"packages":[{"ecosystem":"Packagist","fixed":["2.3.8"],"introduced":["0"],"last_affected":[],"package":"bagisto/bagisto","purl":null,"source":"GHSA-jqrp-58fv-w8cq"},{"ecosystem":"Packagist","fixed":["2.3.8"],"introduced":["0"],"last_affected":[],"package":"bagisto/bagisto","purl":"pkg:composer/bagisto/bagisto","source":"GHSA-jqrp-58fv-w8cq"}],"prev":{"headline":"bagisto - Server Side Template Injection (SSTI) in Product Description","id":"CVE-2025-62416"},"products":["bagisto"],"published":"2025-10-16","related":[{"cvss_score":8.9,"headline":"Bagisto has Normal \u0026 Blind SSTI from low-privilege user when ordering product","id":"CVE-2026-21448","kev_date_added":null,"published":"2026-01-02"},{"cvss_score":8.8,"headline":"Bagisto Missing Authentication on Installer API Endpoints","id":"CVE-2026-21446","kev_date_added":null,"published":"2026-01-02"},{"cvss_score":8.8,"headline":"Bagisto Cross-Site Request Forgery vulnerability","id":"CVE-2023-36237","kev_date_added":null,"published":"2024-02-26"},{"cvss_score":8.8,"headline":"Code injection in n/a","id":"CVE-2023-33570","kev_date_added":null,"published":"2023-06-28"},{"cvss_score":8.8,"headline":"Authorization Bypass Through User-Controlled Key in Bagisto","id":"CVE-2019-16403","kev_date_added":null,"published":"2019-09-18"},{"cvss_score":8.8,"headline":"Bagisto CSRF Vulnerability","id":"CVE-2019-14933","kev_date_added":null,"published":"2019-08-11"},{"cvss_score":8.3,"headline":"Bagisto is vulnerable to XSS through Admin Panel's product creation path","id":"CVE-2025-60880","kev_date_added":null,"published":"2025-10-10"}],"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)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-10-17","vendors":["bagisto"]},"summary":"Attackers can inject malicious formulas into product data, leading to code execution or data exfiltration when victims open exported CSV files in spreadsheet software.","url":"https://insights.sbomify.com/CVE-2025-62417/"}