Insecure password handling vulnerability in Strapi

published 2022-05-03 4 y ago modified 2026-06-17 4 mo ago also GHSA-85vg-grr5-pw42 , EUVD-2022-3114

cvss: 7.5; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 2.9%; EPSS 2.9% chance of exploitation in 30 days, percentile 86%
public exploits: 0; none known

Storing passwords in a recoverable format in the DOCUMENTATION plugin component of Strapi before 3.6.9 and 4.x before 4.1.5 allows an attacker to access a victim's HTTP request, get the victim's cookie, perform a base64 decode on the victim's cookie, and obtain a cleartext password, leading to getting API documentation for further API attacks.

Patch / fix

fixed in 3 links 1

npm strapi 3.6.9
npm @strapi/strapi 4.1.5
strapi strapi 3.6.9, 4.1.5

github.com/strapi/strapi#12246 pull request

Exploit prediction

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

Exploits and checks

packetstormsecurity.com http://packetstormsecurity.com/files/166915/Strapi-3.6.8-Password-Disclosure-Insecure-Handling.html referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by	version	score	vector
NVD	3.1	7.5	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
NVD	2.0	5.0	AV:N/AC:L/Au:N/C:P/I:N/A:N
GitHub	3.1	7.5	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem	package	affected	fixed in
npm	strapi	<3.6.9	3.6.9
npm	@strapi/strapi	>=4.0.0, <4.1.5	4.1.5

Classification

Weakness

CWE-522 Insufficiently Protected Credentials
CWE-922 Insecure Storage of Sensitive Information

References

github.com /strapi/strapi/pull/12246
web, issue-tracking, patch, third-party-advisory
packetstormsecurity.com /files/166915/Strapi-3.6.8-Password-Disclosure-Insecure-Handling.html
web, exploit, third-party-advisory, vdb-entry
strapi.io /
vendor-advisory
hub.docker.com /r/strapi/strapi
web, product, third-party-advisory
nvd.nist.gov /vuln/detail/CVE-2021-46440
advisory
github.com /strapi/strapi
package
strapi.io
web

Sources

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