{"id":51859,"date":"2025-06-14T06:53:00","date_gmt":"2025-06-14T06:53:00","guid":{"rendered":""},"modified":"2025-08-09T05:19:11","modified_gmt":"2025-08-09T11:19:11","slug":"cve-2025-49013-code-injection-vulnerability-in-wilderforge-projects-due-to-unsafe-github-actions-usage","status":"publish","type":"post","link":"https:\/\/www.ameeba.com\/blog\/cve-2025-49013-code-injection-vulnerability-in-wilderforge-projects-due-to-unsafe-github-actions-usage\/","title":{"rendered":"<strong>CVE-2025-49013: Code Injection Vulnerability in WilderForge Projects Due to Unsafe GitHub Actions Usage<\/strong>"},"content":{"rendered":"<p><strong>Overview<\/strong><\/p>\n<p>This post is centered on a critical vulnerability, indexed as CVE-2025-49013, that has been discovered in several projects within the WilderForge organization. The vulnerability arises due to the unsafe use of `${{ github.event.review.body }}` and other user-controlled variables directly within shell script contexts in GitHub Actions workflows. The <a href=\"https:\/\/www.ameeba.com\/blog\/cve-2025-4421-high-severity-vulnerability-discovered-in-lenovo-developed-code\/\"  data-wpil-monitor-id=\"70613\">vulnerability concerns developers<\/a> who maintain or contribute to various repositories within the WilderForge organization, and those who fork these repositories and reuse the affected GitHub Actions workflows. A successful exploit could <a href=\"https:\/\/www.ameeba.com\/blog\/cve-2025-21480-memory-corruption-vulnerability-in-gpu-micronode-leads-to-unauthorized-command-execution\/\"  data-wpil-monitor-id=\"58494\">lead to arbitrary command<\/a> execution, potentially compromising CI infrastructure, secrets, and build outputs.<\/p>\n<p><strong>Vulnerability Summary<\/strong><\/p>\n<p>CVE ID: CVE-2025-49013<br \/>\nSeverity: Critical (CVSS score: 9.9)<br \/>\nAttack Vector: Network<br \/>\nPrivileges Required: None<br \/>\nUser Interaction: Required<br \/>\nImpact: <a href=\"https:\/\/www.ameeba.com\/blog\/cve-2024-45564-critical-memory-corruption-vulnerability-leading-to-potential-system-compromise\/\"  data-wpil-monitor-id=\"58146\">Potential system<\/a> compromise and data leakage<\/p>\n<p><strong>Affected Products<\/strong><\/p><div id=\"ameeb-1856773826\" class=\"ameeb-content-2 ameeb-entity-placement\"><div style=\"border-left: 4px solid #555; padding-left: 20px; margin: 48px 0; font-family: Roboto, sans-serif; color: #ffffff; line-height: 1.6; max-width: 700px;\">\r\n  <h2 style=\"margin-top: 0; font-size: 20px; font-weight: 600; display: flex; align-items: center;\">\r\n    <a href=\"https:\/\/www.ameeba.com\/chat\" style=\"display: inline-flex; align-items: center; margin-right: 8px;\">\r\n      <img decoding=\"async\" src=\"https:\/\/www.ameeba.com\/blog\/wp-content\/uploads\/2025\/10\/Best-App-icon-Ameeba.png\" alt=\"Ameeba Chat Icon\" style=\"width: 40px; height: 40px;\" \/>\r\n    <\/a>\r\n    A new way to communicate\r\n  <\/h2>\r\n\r\n  <p style=\"margin-bottom: 12px;\">\r\n    Ameeba Chat is built on encrypted identity, not personal profiles.\r\n  <\/p>\r\n\r\n  <p style=\"margin-bottom: 16px;\">\r\n    Message, call, share files, and coordinate with identities kept separate.\r\n  <\/p>\r\n\r\n  <ul style=\"list-style: none; padding-left: 0; margin-bottom: 20px;\">\r\n    <li>\u2022 Encrypted identity<\/li>\r\n    <li>\u2022 Ameeba Chat authenticates access<\/li>\r\n    <li>\u2022 Aliases and categories<\/li>\r\n    <li>\u2022 End-to-end encrypted chat, calls, and files<\/li>\r\n    <li>\u2022 Secure notes for sensitive information<\/li>\r\n  <\/ul>\r\n\r\n  <p style=\"font-style: italic; font-weight: 600; margin-bottom: 24px;\">\r\n    Private communication, rethought.\r\n  <\/p>\r\n\r\n  <div style=\"display: flex; flex-wrap: wrap; gap: 12px;\">\r\n    <a href=\"https:\/\/www.ameeba.com\/chat\/download\" style=\"background-color: #ffffff; color: #000000; padding: 10px 20px; text-decoration: none; border-radius: 6px; font-weight: 500;\">Download Ameeba Chat<\/a>\r\n    <a href=\"https:\/\/www.ameeba.com\/chat\" style=\"border: 1px solid #ffffff; color: #ffffff; padding: 10px 20px; text-decoration: none; border-radius: 6px; font-weight: 500;\">Learn More<\/a>\r\n  <\/div>\r\n<\/div>\r\n<\/div>\n<p>Product | Affected Versions<\/p>\n<p>WilderForge\/WilderForge | All Versions<br \/>\nWilderForge\/ExampleMod | All Versions<br \/>\nWilderForge\/WilderWorkspace | All Versions<br \/>\nWilderForge\/WildermythGameProvider | All Versions<br \/>\nWilderForge\/AutoSplitter | All Versions<br \/>\nWilderForge\/SpASM | All Versions<br \/>\nWilderForge\/thrixlvault | All Versions<br \/>\nWilderForge\/MassHash | All Versions<br \/>\nWilderForge\/DLC_Disabler | All Versions<\/p>\n<p><strong>How the Exploit Works<\/strong><\/p>\n<p>The <a href=\"https:\/\/www.ameeba.com\/blog\/cve-2025-24274-input-validation-issue-exploitable-via-malicious-app-on-macos\/\"  data-wpil-monitor-id=\"59614\">exploit works by submitting a maliciously<\/a> crafted pull request review containing shell metacharacters or commands. This enables the attacker to execute <a href=\"https:\/\/www.ameeba.com\/blog\/cve-2025-47933-arbitrary-actions-and-cross-site-scripting-vulnerability-in-argo-cd\/\"  data-wpil-monitor-id=\"58446\">arbitrary shell code on the GitHub Actions<\/a> runner. The <a href=\"https:\/\/www.ameeba.com\/blog\/cve-2025-32106-unauthenticated-remote-code-execution-in-audiocodes-mediapack-mp-11x\/\"  data-wpil-monitor-id=\"58570\">code is executed<\/a> with the permissions of the workflow, potentially compromising the CI infrastructure, secrets, and build outputs.<\/p>\n<p><strong>Conceptual Example Code<\/strong><\/p><div id=\"ameeb-2526117800\" class=\"ameeb-content ameeb-entity-placement\"><div class=\"poptin-embedded\" data-id=\"f6b387694f681\"><\/div>\r\n\r\n\r\n\r\n\r\n\r\n<\/div>\n<p>Here is a<br \/>\n<strong>conceptual<\/strong><br \/>\n example of how the vulnerability might be exploited. In this example, `<<< \"shell command\"` represents the malicious shell command or metacharacters injected into the pull request review.\n\n\n\n<pre><code class=\"\" data-line=\"\">POST \/repos\/WilderForge\/WilderForge\/pulls\/1\/reviews HTTP\/1.1\nHost: api.github.com\nAuthorization: token USER_GITHUB_TOKEN\nAccept: application\/vnd.github.v3+json\nContent-Type: application\/json\n{\n&quot;body&quot;: &quot;${{ github.event.review.body }} &lt;&lt;&lt; \\&quot;shell command\\&quot;&quot;,\n&quot;event&quot;: &quot;APPROVE&quot;\n}<\/code><\/pre>\n<p>This request would submit an approving review for the specified pull request, and if processed by an affected GitHub Actions workflow, would <a href=\"https:\/\/www.ameeba.com\/blog\/cve-2025-45854-arbitrary-code-execution-vulnerability-in-jehc-bpm-2-0-1\/\"  data-wpil-monitor-id=\"58658\">execute the attacker&#8217;s arbitrary<\/a> shell command.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Overview This post is centered on a critical vulnerability, indexed as CVE-2025-49013, that has been discovered in several projects within the WilderForge organization. The vulnerability arises due to the unsafe use of `${{ github.event.review.body }}` and other user-controlled variables directly within shell script contexts in GitHub Actions workflows. The vulnerability concerns developers who maintain or [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"footnotes":""},"categories":[1],"tags":[],"vendor":[79],"product":[],"attack_vector":[78,80],"asset_type":[],"severity":[],"exploit_status":[],"class_list":["post-51859","post","type-post","status-publish","format-standard","hentry","category-uncategorized","vendor-github","attack_vector-injection","attack_vector-rce"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.ameeba.com\/blog\/wp-json\/wp\/v2\/posts\/51859","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.ameeba.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.ameeba.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.ameeba.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.ameeba.com\/blog\/wp-json\/wp\/v2\/comments?post=51859"}],"version-history":[{"count":7,"href":"https:\/\/www.ameeba.com\/blog\/wp-json\/wp\/v2\/posts\/51859\/revisions"}],"predecessor-version":[{"id":63282,"href":"https:\/\/www.ameeba.com\/blog\/wp-json\/wp\/v2\/posts\/51859\/revisions\/63282"}],"wp:attachment":[{"href":"https:\/\/www.ameeba.com\/blog\/wp-json\/wp\/v2\/media?parent=51859"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.ameeba.com\/blog\/wp-json\/wp\/v2\/categories?post=51859"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.ameeba.com\/blog\/wp-json\/wp\/v2\/tags?post=51859"},{"taxonomy":"vendor","embeddable":true,"href":"https:\/\/www.ameeba.com\/blog\/wp-json\/wp\/v2\/vendor?post=51859"},{"taxonomy":"product","embeddable":true,"href":"https:\/\/www.ameeba.com\/blog\/wp-json\/wp\/v2\/product?post=51859"},{"taxonomy":"attack_vector","embeddable":true,"href":"https:\/\/www.ameeba.com\/blog\/wp-json\/wp\/v2\/attack_vector?post=51859"},{"taxonomy":"asset_type","embeddable":true,"href":"https:\/\/www.ameeba.com\/blog\/wp-json\/wp\/v2\/asset_type?post=51859"},{"taxonomy":"severity","embeddable":true,"href":"https:\/\/www.ameeba.com\/blog\/wp-json\/wp\/v2\/severity?post=51859"},{"taxonomy":"exploit_status","embeddable":true,"href":"https:\/\/www.ameeba.com\/blog\/wp-json\/wp\/v2\/exploit_status?post=51859"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}