Impact
The vulnerability allows a malicious pull request author to embed shell metacharacters in the pull‑request's branch name or fork name. Those values are interpolated untrusted into a shell command (gh pr comment) executed by the PR Branch Checker workflow. The injected payload runs with the runner's GITHUB_TOKEN, which has pull‑request write permissions, thus enabling arbitrary command execution on the workflow host. The flaw falls under CWE-78: Improper Neutralization of Input During Command Generation.
Affected Systems
The issue affects the "shriyanss:js-recon" repository. Vulnerable releases range from 1.2.1‑beta.1 through 1.3.1‑beta.2 inclusive. All versions under this range that contain the PR Branch Checker workflow are impacted.
Risk and Exploitability
The published CVSS score of 9.3 classifies this exposure as critical. The EPSS score is not available, but given the ability to run arbitrary code with repository write access, the exploitation risk is high. It is not listed in the CISA KEV catalog. Attackers can trigger it by opening a pull request with a crafted branch or fork name, making the threat vector remote and readily achievable on any public or private GitHub repository utilizing the vulnerable workflow.
OpenCVE Enrichment