GitHub Advisoryadvisory · npm

GHSA-495j-h493-42q2 Strapi Allows Unauthorized Access to Private Fields via parms.lookup

HIGH Published 2025-10-16 Modified 2025-10-16 Official page ↗
Aliases
CVE-2024-56143
Ecosystem
npm
Packages
@strapi/core
Severity
High
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
Weaknesses
CWE-639
Reviewed
2025-10-16

Affected packages

• npm @strapi/core: >= 5.0.0, < 5.5.2 → fixed in 5.5.2

Description

Summary It's possible to access any private fields by filtering through the lookup parameters Details Using the new lookup operator provided by the document service in Strapi 5, it is not properly sanitizing this query operator for private fields. PoC 1. Create a strapi app. 2. Create a content-type 3. In the content-type you make a new entry 4. Go back to the list view 4. Add `&lookup[updatedBy][password][$startsWith]=$2` to the end of your url (All passwords start with $2) see that all entries are still there 6. Add `&lookup[updatedBy][password][$startsWith]=$3` see the entry disappear proving that the search above works Impact An attacker can perform filtering attacks on everything related to the object, including admin passwords and reset-tokens. This means that they can gain full access to the strapi instance.

Related

Alias · CVE (1)

  • CVE-2024-56143 Strapi is an open-source headless content management system. vulnerability

Weakness · CWE (1)

  • CWE-639 Authorization Bypass Through User-Controlled Key weakness

References