Arbitrary Command Injection in strapi/strapi

published 2022-02-26 4 y ago modified 2026-06-17 4 mo ago also GHSA-xrjf-phvv-r4vr , EUVD-2022-1258

cvss: 6.1; version 3.0, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.7%; EPSS 0.7% chance of exploitation in 30 days, percentile 54%
public exploits: 0; none known

Arbitrary Command Injection in GitHub repository strapi/strapi prior to 4.1.0.

Patch / fix

fixed in 2 links 2

npm strapi 4.1.0
strapi strapi/strapi 4.1.0

github.com/strapi/strapi@2a3f5e9 commit
github.com/strapi/strapi@2a3f5e9 commit

Exploit prediction

0.73% chance of exploitation in the next 30 days, higher than 54% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

huntr.dev https://huntr.dev/bounties/001d1c29-805a-4035-93bb-71a0e81da3e5 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by	version	score	vector
CNA	3.0	6.1	CVSS:3.0/AV:L/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:L
NVD	3.1	6.7	CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
NVD	2.0	7.2	AV:L/AC:L/Au:N/C:C/I:C/A:C
GitHub	3.0	6.1	CVSS:3.0/AV:L/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:L

Affected packages

ecosystem	package	affected	fixed in
npm	strapi	<4.1.0	4.1.0

Affected products

strapi strapi/strapi

Classification

Weakness

CWE-78 Improper Neutralization of Special Elements used in an OS Command
CWE-77 Improper Neutralization of Special Elements used in a Command

References

github.com /strapi/strapi/commit/2a3f5e988be6a2c7dae5ac22b9e86d579b462f4c
web, patch, third-party-advisory
github.com /strapi/strapi/commit/2a3f5e988be6a2c7dae5ac22b9e86d579b462f4c
web
huntr.dev /bounties/001d1c29-805a-4035-93bb-71a0e81da3e5
web, exploit, third-party-advisory
github.com /strapi/strapi/issues/12879
web, issue-tracking, third-party-advisory
nvd.nist.gov /vuln/detail/CVE-2022-0764
advisory
github.com /strapi/strapi
package
github.com /strapi/strapi/blob/master/packages/generators/app/lib/utils/fetch-npm-template.js#L13
web

Sources

CVE List CVE-2022-0764
GitHub Advisory GHSA-xrjf-phvv-r4vr
NVD CVE-2022-0764

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary