CVE-2023-22894: Strapi Cleartext Storage of Sensitive Information Vulnerability
Strapi · Strapi · NVD published 2023-04-19 · posted 2026-10-21 · last modified 2026-10-09
What it is
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.
| Weakness | CWE-312 |
|---|---|
| CVSS vector | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N (source: [email protected]) |
| CISA due date | 2026-10-11 (for US federal agencies under BOD; a good deadline for everyone) |
| ATT&CK tactics | n/a |
Step-by-step fix guide: How to fix CVE-2023-22894: Strapi (exploited in the wild)
Exploitation evidence
First exploit evidence seen: 2023-04-24 (earliest date across the sources below).
Exploited in the wild
- CISA KEV: listed since 2026-10-08. Source
Public exploit code
GitHub proof-of-concept repositories
2 public repositories from 2 accounts, first seen 2023-04-24. Most starred: Saboor-Hakimi/CVE-2023-22894 (13 stars), view repository.
Verify before running: public PoCs can be malicious. Read the code and only run it in an isolated lab. A PoC means exploit code is public, not that this CVE is exploited in the wild.
Sources: CISA KEV · nomi-sec/PoC-in-GitHub.
No ATT&CK techniques could be mapped or inferred for this CVE yet.
How to fix it
CISA 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. (source: CISA KEV)
Fixed versions
- strapi strapi: upgrade to 4.8.0 or later (affected from 3.2.1)
Derived from the NVD CPE configuration (versionEndExcluding / versionEndIncluding). Always confirm with the vendor advisory.
Vendor advisories and patches
- https://strapi.io/blog/security-disclosure-of-vulnerabilities-cve (CISA KEV notes)
- https://github.com/strapi/strapi/releases (CISA KEV notes)
Detection Generic guidance
Response checklist Generic guidance
- Inventory: find every instance of the affected product and version (include internet-facing and forgotten ones).
- Patch or mitigate per the vendor advisory; if you cannot patch, remove internet exposure or apply the vendor workaround.
- Assume compromise if the system was exposed before patching: hunt for the indicators in the advisory and review logs back to the disclosure date.
- Rotate credentials and secrets stored on or used by the affected system if compromise cannot be ruled out.