CVE-2025-49013
📋 TL;DR
This CVE describes a critical code injection vulnerability in WilderForge GitHub Actions workflows where user-controlled variables like ${{ github.event.review.body }} are used unsafely in shell script contexts. Attackers can submit malicious pull request reviews containing shell commands to execute arbitrary code on GitHub Actions runners, potentially compromising CI infrastructure, secrets, and build outputs. Only developers/maintainers of affected WilderForge repositories and users who fork/reuse vulnerable workflows are affected; end users of compiled software are not impacted.
💻 Affected Systems
- WilderForge/WilderForge
- WilderForge/ExampleMod
- WilderForge/WilderWorkspace
- WilderForge/WildermythGameProvider
- WilderForge/AutoSplitter
- WilderForge/SpASM
- WilderForge/thrixlvault
- WilderForge/MassHash
- WilderForge/DLC_Disabler
⚠️ Manual Verification Required
This CVE does not have specific version information in our database, so automatic vulnerability detection cannot determine if your system is affected.
Why? The CVE database entry doesn't specify which versions are vulnerable (no version ranges provided by the vendor/NVD).
🔒 Custom verification scripts are available for registered users. Sign up free to download automated test scripts.
- Review the CVE details at NVD
- Check vendor security advisories for your specific version
- Test if the vulnerability is exploitable in your environment
- Consider updating to the latest version as a precaution
⚠️ Risk & Real-World Impact
Worst Case
Complete compromise of GitHub Actions runner with access to repository secrets, ability to modify source code, exfiltrate sensitive data, and pivot to other systems in the CI/CD pipeline.
Likely Case
Execution of arbitrary commands on GitHub Actions runners leading to secret theft, build manipulation, or repository compromise.
If Mitigated
No impact if proper input validation and sanitization are implemented, or if GitHub Actions are disabled for affected repositories.
🎯 Exploit Status
Exploitation requires ability to submit pull request reviews to affected repositories. Public proof-of-concept exists in security advisories and research papers.
🛠️ Fix & Mitigation
✅ Official Fix
Patch Version: Check individual repository security advisories
Vendor Advisory: https://github.com/WilderForge/WilderForge/security/advisories/GHSA-m6r3-c73x-8fw5
Restart Required: No
Instructions:
1. Review GitHub Actions workflows in affected repositories. 2. Replace unsafe usage of ${{ github.event.review.body }} and similar variables with proper sanitization. 3. Follow GitHub's security hardening guidelines for preventing script injection. 4. Update workflows to use GitHub Actions expressions or proper escaping.
🔧 Temporary Workarounds
Disable GitHub Actions
allTemporarily disable GitHub Actions in affected repositories to prevent exploitation
Navigate to repository Settings > Actions > Disable Actions for this repository
Remove Vulnerable Workflows
allDelete or disable affected GitHub Actions workflow files
rm .github/workflows/[vulnerable-workflow-file].yml
🧯 If You Can't Patch
- Disable pull request reviews from untrusted contributors
- Implement manual review process for all pull requests before GitHub Actions execution
🔍 How to Verify
Check if Vulnerable:
Review GitHub Actions workflow files for unsafe usage of ${{ github.event.review.body }} or similar user-controlled variables in shell script contexts without proper sanitization.Check Version:
Review workflow file contents and commit history; no specific version command available.Verify Fix Applied:
Check that workflow files now use proper input validation, GitHub Actions expressions, or appropriate escaping for user-controlled variables.📡 Detection & Monitoring
Log Indicators:
- Unusual shell commands in GitHub Actions logs
- Unexpected environment variable modifications
- Suspicious pull request review activity
Network Indicators:
- Unexpected outbound connections from GitHub Actions runners
- Data exfiltration patterns
SIEM Query:
source="github-actions" AND (command_injection_indicators OR suspicious_shell_patterns)🔗 References
- 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://github.com/WilderForge/WilderForge/security/advisories/GHSA-m6r3-c73x-8fw5
- https://securitylab.github.com/research/github-actions-untrusted-input
