CVE-2024-56143: @strapi/core Strapi Allows Unauthorized Access To Vulnerability

HIGH
Advisory Identifier: GHSA-495j-h493-42q2
Share
CVSS 8.2
CWE-639
Published
Advisory Summary

CVE-2024-56143 is a HIGH (CVSS 8.2) strapi allows unauthorized access to vulnerability (CWE-639: Authorization Bypass Through User-Controlled Key) affecting @strapi/core libraries in the npm ecosystem. The issue involves strapi allows unauthorized access to private fields via parms.lookup. Remediation is available by upgrading affected packages to version 5.5.2.

CVE-2024-56143 at a Glance

CVE Identifier CVE-2024-56143
GHSA Identifier GHSA-495j-h493-42q2
Severity HIGH
CVSS v3.1 Base Score 8.2
CWE Classification CWE-639: Authorization Bypass Through User-Controlled Key
Affected Product @strapi/core
Package Ecosystem npm
Published Date
Last Updated

Security Impact

CVSS: 8.2

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity Low (I:L)
Availability None (A:N)

How to Fix CVE-2024-56143

To remediate this vulnerability, upgrade all affected @strapi/core dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

@strapi/core fixed: 5.5.2 
npm install @strapi/core@5.5.2
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

npm ls @strapi/core

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2024-56143, inspect your project dependencies using npm:

npm ls @strapi/core

Analyze the terminal output to locate any version of @strapi/core in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 5.5.2), your application is affected.

Note: The npm ls @strapi/core command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-639: Authorization Bypass Through User-Controlled Key, where 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. In @strapi/core, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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

CVE-2024-56143 Affected @strapi/core Versions

1 component(s)
Fixed Versions:
5.5.2
Product / Package Ecosystem Affected Versions Fixed Version
@strapi/core
npm/@strapi/core
npm
≥ 5.0.0
< 5.5.2
5.5.2

References

GitHub Advisory / Wiki ADVISORY
https://github.com/strapi/strapi/security/advisories/GHSA-495j-h493-42q2
NVD — CVE-2024-56143 NVD
https://nvd.nist.gov/vuln/detail/CVE-2024-56143
Security Fix Commit FIX COMMIT
https://github.com/strapi/strapi/commit/0c6e0953ae1e62afae9329de7ae6d6a5e21b95b8
@strapi/core Source Repository REPOSITORY
https://github.com/strapi/strapi

Frequently Asked Questions

What is CVE-2024-56143?
CVE-2024-56143 is a security vulnerability in @strapi/core involving Strapi Allows Unauthorized Access to Private Fields via parms.lookup under CWE-639: Authorization Bypass Through User-Controlled Key.
Which @strapi/core versions are affected?
Affected versions include releases prior to 5.5.2 across affected packages: @strapi/core.
What version fixes CVE-2024-56143?
Upgrading to 5.5.2 (or the latest patched release for your respective branch) resolves the vulnerability.
Is @strapi/core affected?
Yes, @strapi/core is affected in releases prior to 5.5.2. Upgrade your dependency to 5.5.2 or later.
What is the CVSS score of CVE-2024-56143?
CVE-2024-56143 has a CVSS v3.1 base score of 8.2 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N.
What CWE is associated with CVE-2024-56143?
CVE-2024-56143 is classified under CWE-639: 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.).
How can I check npm dependencies for CVE-2024-56143?
Run the dependency tree command: 'npm ls @strapi/core'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-495j-h493-42q2",
  "modified" : "2025-10-16T20:42:12Z",
  "published" : "2025-10-16T18:22:40Z",
  "aliases" : [ "CVE-2024-56143" ],
  "summary" : "Strapi Allows Unauthorized Access to Private Fields via parms.lookup",
  "details" : "### Summary\nIt's possible to access any private fields by filtering through the lookup parameters\n\n### Details\n\nUsing the new lookup operator provided by the document service in Strapi 5, it is not properly sanitizing this query operator for private fields.\n\n### PoC\n\n1. Create a strapi app.\n2. Create a content-type\n3. In the content-type you make a new entry\n4. Go back to the list view\n4. Add `&lookup[updatedBy][password][$startsWith]=$2` to the end of your url (All passwords start with $2) see that all entries are still there\n6. Add `&lookup[updatedBy][password][$startsWith]=$3` see the entry disappear proving that the search above works\n\n### Impact\n\nAn 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.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "@strapi/core"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "5.0.0"
      }, {
        "fixed" : "5.5.2"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/strapi/strapi/security/advisories/GHSA-495j-h493-42q2"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2024-56143"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/strapi/strapi/commit/0c6e0953ae1e62afae9329de7ae6d6a5e21b95b8"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/strapi/strapi"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-639" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2025-10-16T18:22:40Z",
    "nvd_published_at" : "2025-10-16T16:15:36Z"
  }
}