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.
The vulnerability results from directly embedding user-controlled input data — such as pull request review content (`github.event.review.body`) — in the `run` sections of GitHub Actions workflows without proper encoding or sanitization. An attacker submitting a review containing shell metacharacters or system commands can cause their execution in the GitHub Actions runner environment. Execution occurs with the permissions of the given workflow, which may include access to repository secrets and build artifacts.
An attacker can execute arbitrary code on a GitHub Actions runner with workflow permissions, potentially gaining access to CI/CD secrets, compromising build infrastructure, and modifying output artifacts. Compiled outputs produced during exploitation may be infected.
Apply patches available from the vendor according to references (advisory GHSA-m6r3-c73x-8fw5). A temporary workaround is to disable GitHub Actions in vulnerable repositories or remove vulnerable workflows. The goal is to replace direct interpolations of user-controlled variables with environment variables and follow GitHub guidelines for hardening security in GitHub Actions.
Repositories WilderForge/WilderForge, WilderForge/ExampleMod, WilderForge/WilderWorkspace, WilderForge/WildermythGameProvider, WilderForge/AutoSplitter, WilderForge/SpASM, WilderForge/thrixlvault, WilderForge/MassHash and WilderForge/DLC_Disabler, as well as forks of these repositories using vulnerable GitHub Actions workflows. The vulnerability affects only developers and contributors — end users installing finished releases are not at risk.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H