NewApp Monitoring is liveSign up free
AgentbeamBeta
Known exploited vulnerability · Strapi

CVE-2023-22894: Strapi Cleartext Storage of Sensitive Information Vulnerability

mediumCVSS 3.1 4.9Exploited

Strapi lets a user with admin panel access filter API queries on private fields such as password and reset_password_token, and read the values back one character at a time. A Super Admin can dump every user's password hash and reset token. Strapi 4.8.0 contains the fix. CISA lists the flaw as exploited in the wild.

Published Apr 19, 2023 · Updated Oct 9, 2026 · Analysis Oct 25, 2026

What an attacker can do

Strapi removed private fields from API responses but not from the query. Filters could still match on them. With an operator like $startsWith, an attacker guesses a value one character at a time and watches whether the number of returned entries changes. That infers hashes and tokens without ever seeing them in a response.

A Super Admin can recover password hashes and reset tokens for admin and API users. An admin whose role can read API users' username and email can recover data for lower-privileged API users, but not for other admins. The write-up by Ghost CCAM goes further: relations like createdBy and updatedBy link entries to admins, so a publicly readable collection that exposes those relations can let an unauthenticated visitor reach admin hashes and tokens.

A leaked Super Admin reset token lets an attacker set a new password and take over the admin account. The same write-up chains this with a separate Strapi email template injection flaw for remote code execution on Strapi 4.5.5 and earlier.

Who is affected

The vendor bulletin lists Strapi 3.2.1 up to, but not including, 4.8.0. The NVD text says "through 4.5.5", so trust the vendor range. Strapi 3.x is end of life and gets no patch.

Check your installed version:

npm ls @strapi/strapi

How to fix it

Upgrade to Strapi 4.8.0 or later. The vendor advises going well past 4.8.0, because later releases fix other flaws. Strapi 3.x users must move to a patched 4.x release. The 4.8.0 fix sanitizes query parameters so private fields are dropped, and it sanitizes column names before queries run.

CISA's required action: apply mitigations per vendor instructions, follow BOD 26-04 and its forensics triage requirements, and stop using the product if mitigations are unavailable. The due date was 2026-10-11 (binding on US federal agencies).

After patching, rotate admin passwords and invalidate reset tokens if you find signs of exploitation.

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.

How to tell if you were hit

The attack travels in GET query strings, so request logs usually capture it. The vendor gives this search:

grep -iE '(\[|%5B)\s*(email|password|reset_password_token|resetPasswordToken)\s*(\]|%5D)' access.log

A single match proves little. Many requests that reference password, reset_password_token or resetPasswordToken suggest hashes and tokens were extracted one character at a time. Strapi says to begin incident response at that point. Also look for unexpected admin password resets.

Original advisory

From the National Vulnerability Database. This product uses the NVD API but is not endorsed or certified by the 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.

Questions

Is CVE-2023-22894 exploited in the wild?

Yes. CISA added it to the Known Exploited Vulnerabilities catalog on 2026-10-08, with a due date of 2026-10-11. It is not tagged as used in ransomware campaigns.

Which Strapi version fixes CVE-2023-22894?

Strapi 4.8.0, released 2023-03-15, contains the fix. The vendor recommends upgrading beyond it, since later versions patch other vulnerabilities. Strapi 3.x is end of life and has no patch.

Does the attacker need to be logged in?

The NVD description requires admin panel access. The Ghost CCAM write-up shows that relations like createdBy can expose admin hashes to unauthenticated users when a public collection returns them.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. The analysis is written by an AI model from the sources listed above and checked by automated rules before it is published. Check versions against the vendor's advisory before you act. Methodology