CVE-2024-29181

1. If a super admin creates a collection where an item in the collection has an association to another collection, a user with the Author Role can see the list of associated items they did not create. They should only see their own items that they created, not all items ever created.

Details

At the top level every collection shows blank items for an Author if they did not create the item. This is ideal and works great. However if you associate one private collection to another private collection and an Author creates a new item. The pull down should not show the admins list of previously created items. It should be blank unitl they add their own items.

PoC

1. Sign in as Admin. Navigate to content creation.
2. Select a collection and verify you have items you created there. And that they have associations to other protected collections.
3. Verify role permissions for your collections are set to CRUD if user created.
4. Log out and sign in as a unrelated Author.
5. Navigate to content management and verify you see collections built by admin but empty for you (as expected)
6. Create a new item as an Author and see the card appear with attributes to fill out.
7. Use the form pull down for the associations.
8. Notice that protected collection items from Admin appear in drop down. These should be hidden

See images below for more context

Permissions set

Good at top level no items seen

Drop down in Author login can see Admin data

Security vulnerability where authors have access to protected data created by admin. This could be passwords emails or any other item created for the admin's collection.

CVE-2024-29181 has a CVSS score of 2.3 (Low). The vector is reachable from an adjacent network, low privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (4.19.1); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2024-29181? CVE-2024-29181 is a low-severity security vulnerability in @strapi/plugin-content-manager (npm), affecting versions < 4.19.1. It is fixed in 4.19.1.
2. How severe is CVE-2024-29181? CVE-2024-29181 has a CVSS score of 2.3 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of @strapi/plugin-content-manager are affected by CVE-2024-29181? @strapi/plugin-content-manager (npm) versions < 4.19.1 is affected.
4. Is there a fix for CVE-2024-29181? Yes. CVE-2024-29181 is fixed in 4.19.1. Upgrade to this version or later.
5. Is CVE-2024-29181 exploitable, and should I be worried? Whether CVE-2024-29181 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2024-29181 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2024-29181? Upgrade @strapi/plugin-content-manager to 4.19.1 or later.

Other vulnerabilities in @strapi/plugin-content-manager