CVE-2023-22894 — Strapi Cleartext Storage of Sensitive Information Vulnerability
Strapi through 4.5.5 allows attackers (with access to the admin panel) to discover sensitive user details by exploiting the query filter. The attacker can filter users by columns that contain sensitive information and infer a value from API responses. If the attacker has super admin access, then this can be exploited to discover the password hash and password reset token of all users. If the attacker has admin panel access to an account with permission to access the username and email of API users with a lower privileged role (e.g., Editor or Author), then this can be exploited to discover sensitive information for all API users but not other admin accounts.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- Confirmed exploitation (CISA KEV)+35
- Public exploit/PoC (github)+6
- EPSS 3.6% (30-day exploitation probability)+13
- Technical severity (medium)+3
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Npm @strapi/strapi: fixed in version 4.8.0 — github.com (GitHub Security Advisories)
CISA required action CISA
Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
US federal deadline: Oct 11, 2026 — passed 4 day(s) ago
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Strapi Strapi, Npm @strapi/strapi).
- Treat as emergency remediation: the CVE is in CISA KEV (confirmed exploitation).
- Apply the fixed version or the patch documented under Remediation.
- Search available logs for exploit probes matching the vulnerability class (info disclosure), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Strapi | Strapi | ≥ 3.2.1 and < 4.8.0 | Vulnerable | NIST National Vulnerability Database |
| Npm | @strapi/strapi | ≥ 3.2.1 and < 4.8.0 | Vulnerable | GitHub Security Advisories |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 7.5 | CVSS 3.1 | High | — | — | GitHub, Inc. via GitHub Security Advisories |
| 7.2 | CVSS 3.1 | High | 1.2 | 5.9 | 134c704f-9b21-4f2e-91b3-4a467353bcc0 via NIST National Vulnerability Database |
| 7.2 | CVSS 3.1 | High | — | — | CISA-ADP via CVE Program (cve.org) e CISA ADP |
| 4.9 | CVSS 3.1 | Medium | 1.2 | 3.6 | nvd@nist.gov via NIST National Vulnerability Database |
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N (score shown at the top: nvd@nist.gov) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
CISA KEV details CISA
CISA lists a CVE once it has evidence of exploitation against real targets.
CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a reference date.
Public exploits, PoCs and detection templates
Public code that demonstrates or tests the flaw raises the odds of mass exploitation — and Nuclei templates help find vulnerable assets in your environment.
- CVE-2023-22894 ★ 13 Apr 24, 2023
- maxntv/CVE-2023-22894-PoC ★ 0 Jul 31, 2025
Warning: public PoCs are sometimes disguised malware. Use them only for authorized testing in an isolated environment. This portal does not host exploit code — it only points to the sources.
EPSS over time FIRST
Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 3.61%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
- Look for anomalous data read/export volumes and access to sensitive records.
- Hunt retroactively in logs from before Oct 8, 2026 (KEV listing): exploitation may have started earlier.
Timeline
What happened to this CVE, newest first.
- 2026
- SSVC assessment updated
- Fix documented
- Affected products added · npm/@strapi/strapi
- Record published
- Affected products added · strapi/strapi
- CVSS changed · 4.9
- Source status changed · → Analyzed
- Added to CISA KEV (detected)
- Record created in this database
- Added to CISA KEV catalog
- 2023
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 2× References added · Oct 13, 2026 – Oct 13, 2026
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
8 on the record
- strapi.io/blog/security-disclosure-of-vulnerabilities-cve
- www.cisa.gov/known-exploited-vulnerabilities-catalog
- www.ghostccamm.com/blog/multi_strapi_vulns/
- nvd.nist.gov/vuln/detail/CVE-2023-22894
- github.com/strapi/strapi/security/advisories/GHSA-jjqf-j4w7-92w8
- github.com/advisories/GHSA-jjqf-j4w7-92w8
- github.com/strapi/strapi/releases
- github.com/strapi/strapi/releases/tag/v4.8.0
Elsewhere on this site
Related CVEs (same products)
- Medium CVE-2026-108114 Strapi 5.47.0 through 5.57.0 Improper Authorization via Admin API Token Field Permissions 5d
- Medium CVE-2026-57997 Strapi users-permissions - JWT Algorithm Confusion via Missing Algorithm Configuration Jun 29, 2026
- High CVE-2026-27886 Strapi may leak sensitive data via relational filtering due to lack of query sanitization May 14, 2026
- Medium CVE-2026-22706 Strapi: Password Reset Does Not Revoke Existing Refresh Sessions May 14, 2026
- Medium CVE-2026-22707 Strapi Upload Plugin MIME Validation Bypass via Content API May 14, 2026
- Medium CVE-2025-64526 Strapi has a rate limit bypass on users-permissions plugin via attacker-controlled email keying May 14, 2026
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2023-22894 is "Strapi Cleartext Storage of Sensitive Information Vulnerability", rated Medium. It affects Strapi (Strapi); versions are in the scope table. It is in CISA KEV: there is evidence of real-world exploitation. CVSS 4.9 describes technical severity. EPSS 3.61% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.