{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-15099 exists.","fix":"No fix has been published for CVE-2025-15099 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-15099 is a medium-severity authentication bypass vulnerability in simstudioai sim, published on 26 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-15099 and fix it if it is affected.\n\nWhat it is: CVE-2025-15099 is a medium-severity authentication bypass vulnerability in simstudioai sim, published on 26 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-15099 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-15099/ (Markdown: https://insights.sbomify.com/CVE-2025-15099/index.md)","id":"CVE-2025-15099","markdown":"https://insights.sbomify.com/CVE-2025-15099/index.md","name":"CVE-2025-15099","record":{"aliases":["GHSA-2hg8-9339-xpwg"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"simstudioai sim","requires_auth":"none","summary":"Attackers can bypass authentication in the CRON Secret Handler by manipulating the internal API secret, requiring a patch to secure the application.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[{"product":"sim","vendor":"sim"}],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P","version":"4.0"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"}],"description":"A vulnerability was identified in simstudioai sim up to 0.5.27. This vulnerability affects unknown code of the file apps/sim/lib/auth/internal.ts of the component CRON Secret Handler. The manipulation of the argument INTERNAL_API_SECRET leads to improper authentication. It is possible to initiate the attack remotely. The exploit is publicly available and might be used. The identifier of the patch is e359dc2946b12ed5e45a0ec9c95ecf91bd18502a. Applying a patch is the recommended action to fix 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 CRON Secret internal.ts improper authentication","id":"CVE-2025-15099","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2025"},"n_packages":0,"n_references":7,"next":{"headline":"JAY Login \u0026 Register \u003c= 2.6.03 - Authenticated (Subscriber+) Privilege Escalation via jay_panel_ajax_update_profile","id":"CVE-2025-15100"},"packages":[],"prev":{"headline":"YunaiV yudao-cloud Business Process Management BpmSyncHttpRequestTrigger server-side request forgery","id":"CVE-2025-15098"},"products":["sim"],"published":"2025-12-26","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 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"},{"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":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-12-26","vendors":["simstudioai"]},"summary":"Attackers can bypass authentication in the CRON Secret Handler by manipulating the internal API secret, requiring a patch to secure the application.","url":"https://insights.sbomify.com/CVE-2025-15099/"}