NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · npm

CVE-2024-56143: Strapi Allows Unauthorized Access to Private Fields via parms.lookup

highCVSS 3.1 8.2GHSA-495j-h493-42q2

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.

Published Oct 16, 2025

Affected packages

@strapi/core

Ecosystem
npm
Affected
>= 5.0.0, < 5.5.2
Fixed in
5.5.2
Check
npm ls @strapi/core

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

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
  5. 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.

Credited to Boegie19, alexandrebodin, derrickmehaffy.

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. No analysis has been written for this entry yet. Methodology

More npm vulnerabilities

All npm entries