ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2023-30623

Arbitrary command injection in embano1/wip

Published Apr 24, 2023 · catalog updated Sep 10, 2026 · Arbitrary command injection in

Check if you run it

No confirmed exploitation is on record for CVE-2023-30623. EPSS is 3.73%. Act only if a listed version of Arbitrary command injection in is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (Arbitrary command injection in).
  • No version range is stored. A customer cannot check an installed version against this record.
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
High8.8
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
3.73%
Remediation
Advisory link
Affected products
GitHub Actions embano1/wip

## Summary The action uses the parameter in an insecure way. The title parameter is used in a run statement - resulting in a command injection vulnerability due to string interpolation. ## Details and Impact This vulnerability can be triggered by any user on GitHub. They just need to create a pull request with a commit message containing an exploit. (Note that first-time PR requests will not be run - but the attacker can submit a valid PR before submitting an invalid PR). The commit can be genuine, but the commit message can be malicious. This can be used to execute code on the GitHub runners (potentially use it for crypto-mining, and waste your resources) and can be used to exfiltrate any secrets that you use in the CI pipeline (including repository tokens). [Here](https://securitylab.github.com/research/github-actions-untrusted-input/) is a set of blog posts by Github's security team explaining this issue. ## How to update existing workflows Replace the following line in your workflow using this action with the branch name or commit pointing to this branch: Or using the exact commit:

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • GitHub Actions embano1/wip0 → 2

How to fix CVE-2023-30623

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2023-30623. EPSS is 3.73%. Act only if a listed version of Arbitrary command injection in is installed.

Which versions are affected?

Compare what you have installed with 0 → 2. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-77: Command Injection. EPSS 3.73%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Apr 24, 2023 · GitHub Advisory Database

    Detected

    ## Summary The action uses the parameter in an insecure way. The title parameter is used in a run statement - resulting in a command injection vulnerability due to string interpolation. ## Details and Impact This vulnerability can be triggered by any user on GitHub. They just need to create a pull request with a commit message containing an exploit. (Note that first-time PR requests will not be ru

  2. Sep 10, 2026 · GitHub Advisory Database

    Fix available

    embano1/wip fixed in 2

  3. Sep 10, 2026 · GitHub Advisory Database

    Fix available

    embano1/wip fixed in 2

  4. Sep 10, 2026 · GitHub Advisory Database

    Updated

    ## Summary The action uses the parameter in an insecure way. The title parameter is used in a run statement - resulting in a command injection vulnerability due to string interpolation. ## Details and Impact This vulnerability can be triggered by any user on GitHub. They just need to create a pull request with a commit message containing an exploit. (Note that first-time PR requests will not be ru

Sources

References

Freshness

Last verified in this catalog Oct 16, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.