CodeceptJS's incomprehensive sanitation can lead to Command InjectionGHSA-34w8-mcwr-vg29
CRITICALFix: codeceptjs/CodeceptJS#3604GHSA-34w8-mcwr-vg29 is a critical-severity (CVSS 9.8) CWE-77 vulnerability in codeceptjs. A fix is available for codeceptjs — see the affected versions and patch details below.
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- A successful exploit gives an attacker total control of the affected component, not partial access.
Exploitation and automatability from CISA’s SSVC triage for GHSA-34w8-mcwr-vg29.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
codeceptjsnpmDescription
CodeceptJS versions 3.5.0 through 3.7.5-beta.18 contain a command injection vulnerability in the emptyFolder function (lib/utils.js). The execSync command directly concatenates the user-controlled directoryPath parameter without sanitization or escaping, allowing attackers to execute arbitrary commands.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | codeceptjs | ≥ 3.5.0&&< 3.7.5 | 3.7.5npm install codeceptjs@3.7.5 |
Affected Products
codeceptjscodeceptDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for codeceptjs, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update codeceptjs to 3.7.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-34w8-mcwr-vg29 is resolved across your whole dependency graph.
Workarounds
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.
Frequently Asked Questions
Is GHSA-34w8-mcwr-vg29 in your dependencies?
Find it across npm, including transitive dependencies.