CVE-2024-29181: @strapi/plugin-content-manager leaks data via relations via the Admin Panel

Published Jun 12, 2024
·
Updated

Summary 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

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

See images below for more context

Permissions set !image

Good at top level no items seen !image

Drop down in Author login can see Admin data !image

Other sources

Strapi is an open-source content management system. Prior to version 4.19.1, a super admin can create a collection where an item in the collection has an association to another collection. When this happens, another user with Author Role can see the list of associated items they did not create. They should see nothing but their own items they created not all items ever created. Users should upgrade @strapi/plugin-content-manager to version 4.19.1 to receive a patch.

NVD

Affected Software

2 affected componentsFixes available
npm/@strapi/plugin-content-manager<4.19.1
4.19.1
Strapi Strapi<4.19.1

Event History

Jun 12, 2024
CVE Published
via MITRE·02:46 PM
Data Sourced
via MITRE·02:46 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·03:15 PM
DescriptionSeverityWeakness
Advisory Published
via GitHub·07:38 PM

Frequently Asked Questions

1

What is the severity of CVE-2024-29181?

CVE-2024-29181 has a medium severity level indicating potential exposure of sensitive data.

2

How do I fix CVE-2024-29181?

To fix CVE-2024-29181, update Strapi to version 4.19.1 or later.

3

What systems are affected by CVE-2024-29181?

CVE-2024-29181 affects Strapi version lower than 4.19.1, particularly those using the @strapi/plugin-content-manager.

4

What is the nature of the vulnerability in CVE-2024-29181?

CVE-2024-29181 allows users with the Author Role to view associated items they did not create.

5

Who is impacted by CVE-2024-29181?

Users with the Author Role in Strapi can be impacted by CVE-2024-29181 due to improper access control.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203