Skip to content

Strapi Allows Unauthorized Access to Private Fields via parms.lookup

High severity GitHub Reviewed Published Oct 16, 2025 in strapi/strapi • Updated Oct 16, 2025

Package

npm @strapi/core (npm)

Affected versions

>= 5.0.0, < 5.5.2

Patched versions

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

References

@cache-your-dreams cache-your-dreams published to strapi/strapi Oct 16, 2025
Published by the National Vulnerability Database Oct 16, 2025
Published to the GitHub Advisory Database Oct 16, 2025
Reviewed Oct 16, 2025
Last updated Oct 16, 2025

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(8th percentile)

Weaknesses

Authorization Bypass Through User-Controlled Key

The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data. Learn more on MITRE.

CVE ID

CVE-2024-56143

GHSA ID

GHSA-495j-h493-42q2

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.