{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-10096 exists.","fix":"No fix has been published for CVE-2025-10096 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-10096 is a medium-severity server-side request forgery 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-10096 and fix it if it is affected.\n\nWhat it is: CVE-2025-10096 is a medium-severity server-side request forgery 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-10096 exists.\n\nAffected product: SimStudioAI sim. 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-2025-10096/ (Markdown: https://insights.sbomify.com/CVE-2025-10096/index.md)","id":"CVE-2025-10096","markdown":"https://insights.sbomify.com/CVE-2025-10096/index.md","name":"CVE-2025-10096","record":{"aliases":["GHSA-q6wr-6g7v-9pxw"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"SimStudioAI sim","requires_auth":"low_privilege","summary":"Remote attackers can exploit a server-side request forgery vulnerability in SimStudioAI sim to access internal resources or bypass security controls.","user_interaction":"not_required","vuln_class":"ssrf"},"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:P","version":"4.0"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"A vulnerability was determined in SimStudioAI sim up to 1.0.0. This affects an unknown function of the file apps/sim/app/api/files/parse/route.ts. Executing manipulation of the argument filePath can lead to server-side request forgery. The attack can be executed remotely. The exploit has been publicly disclosed and may be utilized. This patch is called 3424a338b763115f0269b209e777608e4cd31785. Applying a patch is advised to resolve this issue.","ecosystems":[],"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 server-side request forgery","id":"CVE-2025-10096","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2025"},"n_packages":0,"n_references":6,"next":{"headline":"SimStudioAI sim route.ts code injection","id":"CVE-2025-10097"},"packages":[],"prev":{"headline":"SQL injection in SMPP component of SMSEagle firmware","id":"CVE-2025-10095"},"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 code injection","id":"CVE-2025-10097","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":"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-08","vendors":["SimStudioAI"]},"summary":"Remote attackers can exploit a server-side request forgery vulnerability in SimStudioAI sim to access internal resources or bypass security controls.","url":"https://insights.sbomify.com/CVE-2025-10096/"}