{"answers":{"affected":"2 open source packages ship an affected version, including simstudio. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-10097 exists.","fix":"No fix has been published for CVE-2025-10097 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-10097 is a medium-severity code injection vulnerability in SimStudioAI sim, published on 8 Sep 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-10097 and fix it if it is affected.\n\nWhat it is: CVE-2025-10097 is a medium-severity code injection vulnerability in SimStudioAI sim, published on 8 Sep 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-10097 exists.\n\nAffected packages and fixed versions:\n- simstudio (npm): affected all versions up to 0.1.19; no fix listed\n- simstudio (npm): affected all versions up to 0.1.19; 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-2025-10097/ (Markdown: https://insights.sbomify.com/CVE-2025-10097/index.md)","id":"CVE-2025-10097","markdown":"https://insights.sbomify.com/CVE-2025-10097/index.md","name":"CVE-2025-10097","record":{"aliases":["GHSA-g4c9-f287-64xg"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"SimStudioAI sim","requires_auth":"low_privilege","summary":"Remote attackers can execute arbitrary code via the code argument in the SimStudioAI sim application's API route.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[{"product":"sim","vendor":"sim"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X","version":"4.0"},"cwes":[{"id":"CWE-94","name":"Improper Control of Generation of Code"},{"id":"CWE-74","name":"Improper Neutralization of Special Elements in Output Used by a Downstream Component"}],"description":"A vulnerability was identified in SimStudioAI sim up to 1.0.0. This impacts an unknown function of the file apps/sim/app/api/function/execute/route.ts. The manipulation of the argument code leads to code injection. The attack is possible to be carried out remotely.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"SimStudioAI sim route.ts code injection","id":"CVE-2025-10097","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"code_injection","year":"2025"},"n_packages":2,"n_references":5,"next":{"headline":"PHPGurukul User Management System edit-user-profile.php sql injection","id":"CVE-2025-10098"},"packages":[{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["0.1.19"],"package":"simstudio","purl":null,"source":"GHSA-g4c9-f287-64xg"},{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["0.1.19"],"package":"simstudio","purl":"pkg:npm/simstudio","source":"GHSA-g4c9-f287-64xg"}],"prev":{"headline":"SimStudioAI sim route.ts server-side request forgery","id":"CVE-2025-10096"},"products":["sim"],"published":"2025-09-08","related":[{"cvss_score":9.8,"headline":"Sim Studio AI - MongoDB SSRF and Arbitrary Document Deletion","id":"CVE-2026-3431","kev_date_added":null,"published":"2026-03-02"},{"cvss_score":9.3,"headline":"Sim Studio AI - Unauthenticated OAuth Token Theft","id":"CVE-2026-3432","kev_date_added":null,"published":"2026-03-02"},{"cvss_score":6.9,"headline":"simstudioai sim CRON Secret internal.ts improper authentication","id":"CVE-2025-15099","kev_date_added":null,"published":"2025-12-26"},{"cvss_score":6.9,"headline":"SimStudioAI sim route.ts handleLocalFile path traversal","id":"CVE-2025-7107","kev_date_added":null,"published":"2025-07-07"},{"cvss_score":6.9,"headline":"SimStudioAI sim Session route.ts POST missing authentication","id":"CVE-2025-7114","kev_date_added":null,"published":"2025-07-07"},{"cvss_score":5.3,"headline":"SimStudioAI sim route.ts server-side request forgery","id":"CVE-2025-10096","kev_date_added":null,"published":"2025-09-08"}],"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":"partial"},"state":"PUBLISHED","updated":"2025-09-09","vendors":["SimStudioAI"]},"summary":"Remote attackers can execute arbitrary code via the code argument in the SimStudioAI sim application's API route.","url":"https://insights.sbomify.com/CVE-2025-10097/"}