Quick answers
- Is CVE-2025-10097 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-10097 being exploited in the wild.
- How severe is CVE-2025-10097?
- Low severity, with a CVSS score of 3.1, published 8 September 2025.
- Which products and versions are affected?
- simstudio (npm) SEMVER:introduced=0,last_affected=0.1.19; SimStudioAI Sim 0.1.19 and prior.
- Is there a fix for CVE-2025-10097?
- A patch was published on 2025-09-15: Fix available in pull request #1149 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2025-10097 attacked?
- It is attacked over the network.
- Am I affected by CVE-2025-10097?
- Check whether you run simstudio (npm) or SimStudioAI Sim at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability exists in the POST endpoint `/api/function/execute` in the route.ts file, where the `code` parameter from the request body is directly embedded into a Node.js Script context without sanitization, validation, or filtering (CWE-74, CWE-94). The vulnerable code concatenates user-supplied input into a JavaScript string that is then executed via the `script.runInContext()` method. The attack is network-accessible and requires no authentication; an attacker can craft a POST request with malicious JavaScript code in the `code` parameter to execute arbitrary Node.js code, including spawning child processes and executing system commands. A proof-of-concept demonstrates executing arbitrary shell commands with full process privileges. The vulnerability was patched in pull request #1149.
Affected products
- SimStudioAI sim 0.1.19 and prior
Identifiers
- CVE-2025-10097
- GHSA-g4c9-f287-64xg
Timeline
- 2025-09-08: disclosed: Vulnerability published in GHSA-g4c9-f287-64xg
- 2025-08-14: other: RCE vulnerability discovered and reported as issue #961
- 2025-09-15: patched: Fix available in pull request #1149