Skip to main content
VulnerabilityPublished

CVE-2025-49013: WilderForge · Code Injection

Affects WilderForgeSource CVE Database V5

0

Not known to be exploited · CVSS 10.0 Critical.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
10.0Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.7% chance of exploitation in 30 days – higher than 55% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 9 Jun 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

AI-suggested

  1. Immediately disable GitHub Actions workflows in all affected repositories and forks until patched workflows are available.
  2. Remove or refactor any usage of user-controlled variables directly interpolated into shell scripts in GitHub Actions workflows. Use safe parameterization or environment variables with proper escaping.
  3. Implement strict input validation and sanitization on all user inputs that influence CI workflows.
  4. Restrict permissions of GitHub Actions runners to the minimum necessary, avoiding storage of sensitive secrets in workflows where possible.
  5. Monitor GitHub Actions logs and pull request reviews for suspicious activity indicative of exploitation attempts.
  6. Update all affected WilderForge components and plugins to their fixed versions as soon as patches are released.
  7. Educate developers and maintainers about secure coding practices in CI/CD pipelines, emphasizing the dangers of code injection in automation scripts.
  8. Consider using GitHub’s security features such as required reviewers and branch protection rules to limit who can submit pull request reviews that trigger workflows.
  9. Audit forks and downstream projects that reuse these workflows to ensure they are not vulnerable.
  10. Employ runtime monitoring and anomaly detection on CI infrastructure to detect unusual command executions.

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.

References

Community reviews

Loading reviews…