DE EN IT

~/exploited / cve-2023-22894

CVE-2023-22894: Strapi

According to CISA this vulnerability is already used in attacks (added on 8 October 2026).

Key facts

CVECVE-2023-22894
VendorStrapi — Strapi
VulnerabilityStrapi Cleartext Storage of Sensitive Information Vulnerability
Added8 October 2026
Deadline (US agencies)11 October 2026
Ransomware campaignsunknown

Technical data (NVD, FIRST EPSS)

CVSS base score4.9 (medium) · CVSS 3.1
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N
Attack over the network, complexity: low, privileges: high needed, user interaction: none
EPSS (exploitation probability)Probability of exploitation in the next 30 days: 4.11%. Higher than 91% of all scored vulnerabilities (as of 18 November 2026). A low value is no all-clear: CISA already lists this flaw as exploited in attacks.
Weakness type (CWE)CWE-312
Affected versionsstrapi: >= 3.2.1, < 4.8.0

Description (NVD)

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.

Patches and vendor advisories

Description (CISA)

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.

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.

What admins should do now

  1. Affected? Check whether Strapi is in use and which version runs (package manager, admin UI, --version).
  2. Apply the vendor patch or workaround as soon as it exists. If that is not possible right away: restrict outside access (firewall, VPN, reverse proxy).
  3. Review logs back to 8 October 2026: unusual logins, new files, unexpected processes, outbound connections.
  4. If you suspect a compromise: isolate the system, rotate credentials, check the last backup from before the incident.

The deadline applies to US federal agencies. It is still a useful yardstick for everyone: when a flaw is attacked in the wild, waiting is not an option.

Sources

New articles by e-mail

One e-mail per new article. No tracking, unsubscribe any time. As a thank-you after confirming: my “Server operations & patching” checklist (PDF).