CVE-2019-19609 is a high-severity (CVSS 7.2) OS Command Injection vulnerability in strapi. 12 public exploit references exist, so weaponization risk is real. A fix is available for strapi — see the affected versions and patch details below.
Command Injection in strapi
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2019-19609 by exploitation likelihood (EPSS) against impact (CVSS). In the shaded patch-first corner (EPSS 50%+, CVSS 7.0+).
Where this sits among everything scored
Of 385,738 CVEs with a current EPSS score, this one falls in the 50–90% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.
strapinpmDescription
Versions of strapi before 3.0.0-beta.17.8 are vulnerable to Command Injection. The package fails to sanitize plugin names in the /admin/plugins/install/ route. This may allow an authenticated attacker with admin privileges to run arbitrary commands in the server.
Recommendation
Upgrade to version 3.0.0-beta.17.8 or later
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | strapi | all versions | 3.0.0-beta.17.8npm install strapi@3.0.0-beta.17.8 |
Affected Products
strapistrapiResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Strapi 3.0.0-beta.17.7 - Remote Code Execution (RCE) (Authenticated)
by David Utón · Aug 30, 2021
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for strapi, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update strapi to 3.0.0-beta.17.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-19609 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 CVE-2019-19609 in your dependencies?
Find it across npm, including transitive dependencies.