Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By GitHub_M

  2. · 11 days later

    Published

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2025-49013, by who scored it
Scored byCVSSScoreVector
GitHub_MCNA (assigner)3.1Critical10.0CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
NVDNVD · Deferred3.1Critical9.9CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.86% · top 41% of all CVEs (12 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: yes · Technical impact: total
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Critical 10.0.

Affected products

  • WilderForge · WilderForge

    • affected < 5.2.1.0 (com.wildermods.workspace:com.wildermods.workspace.gradle.plugin)
    • affected < 1.0.0.5 (com.wildermods:ExampleMod)
    • affected < 0.4.2.0 (com.wildermods:WilderForge)
    • affected < 36a1107de6a77f8353dd0aa14690aa3c7c3550ef (com.wildermods:autosplitter)
    • affected < 1.0.1.0 (com.wildermods:dlc_disabler)
    • affected < 1.3.1.0 (com.wildermods:masshash)
    • affected < 1.9.1.0 (com.wildermods:provider)
    • affected < 0.5.1.0 (com.wildermods:thrixlvault)

References

References5

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-49013 badge
[![CVE-2025-49013](https://cveledger.app/badge/CVE-2025-49013.svg)](https://cveledger.app/cve/CVE-2025-49013)

Record last updated .