How severe is GHSA-rg3q-prf8-qxmp?

GHSA-rg3q-prf8-qxmp has a CVSS score of 8.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-rg3q-prf8-qxmp?

GHSA-rg3q-prf8-qxmp affects the following packages: embano1/wip (GitHub Actions). Ecosystems affected: GitHub Actions.

How do I fix GHSA-rg3q-prf8-qxmp?

Update embano1/wip to 2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rg3q-prf8-qxmp is resolved across your whole dependency graph.

How do I detect GHSA-rg3q-prf8-qxmp in my GitHub Actions dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for embano1/wip. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-rg3q-prf8-qxmp if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-rg3q-prf8-qxmp?

O3 pinpoints whether GHSA-rg3q-prf8-qxmp is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-rg3q-prf8-qxmp actively exploited in the wild?

Yes. There are 1 known exploit references for GHSA-rg3q-prf8-qxmp, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for GHSA-rg3q-prf8-qxmp?

GHSA-rg3q-prf8-qxmp has an EPSS (Exploit Prediction Scoring System) score of 3.7%, placing it in the 88th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

When was GHSA-rg3q-prf8-qxmp published, and has it been updated?

GHSA-rg3q-prf8-qxmp was published on April 24, 2023 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 GitHub Actions

GHSA-rg3q-prf8-qxmp

HIGH

Arbitrary command injection in embano1/wip

Also known asCVE-2023-30623

Published

Apr 24, 2023

Updated

Nov 8, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

EPSS Exploitation Probability

via FIRST.org ↗

3.7%probability of exploitation in next 30 days

Lower Risk88th percentile-0.89%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

1 pkg affected

📦embano1/wip

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects GitHub Actions packages — download data is not available via public APIs for these ecosystems.

Description

Summary

The embano1/wip action uses the github.event.pull_request.title 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 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 v2 branch name or commit pointing to this branch:

    uses: embano1/wip@v2

Or using the exact commit:

    uses: embano1/wip@c25450f77ed02c20d00b76ee3b33ff43838739a2 # v2

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦GitHub Actions	`embano1/wip`	all versions	2

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

`embano1/wip` is a GitHub Action written in Bash. Prior to version 2, th…

securitylab.github.comNVDMay 2023

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for embano1/wip. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update embano1/wip to 2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rg3q-prf8-qxmp is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-rg3q-prf8-qxmp is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-rg3q-prf8-qxmp. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

## Summary The `embano1/wip` action uses the `github.event.pull_request.title` 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. Thi

O3 Security · Impact-Aware SCA

Is GHSA-rg3q-prf8-qxmp in your dependencies?

O3 detects GHSA-rg3q-prf8-qxmp across GitHub Actions dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works