CVE-2023-22894: Strapi Cleartext Storage of Sensitive Information Vulnerability
Strapi contains a cleartext storage of sensitive information vulnerability that could allow attackers with access to the admin panel to discover sensitive user details via the query filter. The impacted product(s) could be end-of-life (EoL) and/or end-of-service (EoS). Users are advised to discontinue use and/or transition to a supported version. This vulnerability can be chained with CVE-2023-22621 to achieve remote code execution.
| Vendor | Strapi |
|---|---|
| Product | Strapi |
| Date added to KEV | 2026-10-08 |
| Due date (BOD 22-01) | 2026-10-11 |
| Known ransomware campaign use | Unknown |
| CWE | CWE-312 |
| Required action | 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. |
What to do
- Identify every instance of Strapi Strapi in your environment (asset inventory, EDR, vulnerability scanner).
- Apply CISA's required action: 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.
- Federal civilian agencies must act by 2026-10-11 under BOD 22-01; other organizations can use the same date as a target.
- Check the vendor advisory and NVD entry linked below for affected versions, then record the fix in your change log.
Patching one CVE is step one. Harden your cloud identity baseline too: Free M365 & Google Workspace hardening checklist (Runbook Foundry).
Sources
- NVD entry for CVE-2023-22894 (severity scores, if any, live there)
- CISA KEV catalog entry
- https://strapi.io/blog/security-disclosure-of-vulnerabilities-cve
- https://github.com/strapi/strapi/releases
- https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk
- https://www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizing-security-updates-based-risk
- https://nvd.nist.gov/vuln/detail/CVE-2023-22894