{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-49013 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-49013 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-49013 is a critical code injection vulnerability in WilderForge, published on 9 Jun 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-49013 and fix it if it is affected.\n\nWhat it is: CVE-2025-49013 is a critical code injection vulnerability in WilderForge, published on 9 Jun 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-49013 in the wild and no public exploit code.\n\nAffected product: WilderForge. 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-49013/ (Markdown: https://insights.sbomify.com/CVE-2025-49013/index.md)","id":"CVE-2025-49013","markdown":"https://insights.sbomify.com/CVE-2025-49013/index.md","name":"CVE-2025-49013","record":{"aliases":[],"analysis":{"component_type":"developer_tool","fix_type":"configuration_change","impacts":["code_execution","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"GitHub Actions workflows","requires_auth":"low_privilege","summary":"Attackers can execute arbitrary shell code on CI runners via crafted pull request reviews, compromising secrets and build infrastructure in WilderForge repositories.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":10,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-95","name":"Improper Neutralization of Directives in Dynamically Evaluated Code"},{"id":"CWE-94","name":"Improper Control of Generation of Code"},{"id":"CWE-116","name":"Improper Encoding or Escaping of Output"}],"description":"WilderForge is a Wildermyth coremodding API. A critical vulnerability has been identified in multiple projects across the WilderForge organization. The issue arises from unsafe usage of `${{ github.event.review.body }}` and other user controlled variables directly inside shell script contexts in GitHub Actions workflows. This introduces a code injection vulnerability: a malicious actor submitting a crafted pull request review containing shell metacharacters or commands could execute arbitrary shell code on the GitHub Actions runner. This can lead to arbitrary command execution with the permissions of the workflow, potentially compromising CI infrastructure, secrets, and build outputs. Developers who maintain or contribute to the repos WilderForge/WilderForge, WilderForge/ExampleMod, WilderForge/WilderWorkspace, WilderForge/WildermythGameProvider, WilderForge/AutoSplitter, WilderForge/SpASM, WilderForge/thrixlvault, WilderForge/MassHash, and/or WilderForge/DLC_Disabler; as well as users who fork any of the above repositories and reuse affected GitHub Actions workflows, are affected. End users of any the above software and users who only install pre-built releases or artifacts are not affected. This vulnerability does not impact runtime behavior of the software or compiled outputs unless those outputs were produced during exploitation of this vulnerability. A current workaround is to disable GitHub Actions in affected repositories, or remove the affected workflows.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"WilderForge vulnerable to code Injection via GitHub Actions Workflows","id":"CVE-2025-49013","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2025"},"n_packages":0,"n_references":5,"next":{"headline":"jq heap use after free vulnerability in f_strflocaltime","id":"CVE-2025-49014"},"packages":[],"prev":{"headline":"Himmelblau's Name-Based Group Matching in `pam_allow_groups` Leads to Potential Security Bypass","id":"CVE-2025-49012"},"products":["WilderForge"],"published":"2025-06-09","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-06-09","vendors":["WilderForge"]},"summary":"Attackers can execute arbitrary shell code on CI runners via crafted pull request reviews, compromising secrets and build infrastructure in WilderForge repositories.","url":"https://insights.sbomify.com/CVE-2025-49013/"}