VulnerableCode Package Details - pkg:npm/%40strapi/plugin-content-manager@4.10.1

Search for packages

Vulnerability	Summary	Fixed by
VCID-a54s-xn6b-eycd Aliases: CVE-2024-29181 GHSA-6j89-frxc-q26m	@strapi/plugin-content-manager leaks data via relations via the Admin Panel 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.	4.19.1 Affected by 0 other vulnerabilities.
VCID-adab-ztym-ayhd Aliases: CVE-2023-36472 GHSA-v8gg-4mq2-88q4	Strapi may leak sensitive user information, user reset password, tokens via content-manager views Attackers can get access to user reset password tokens if they have the configure view permissions.	4.11.7 Affected by 2 other vulnerabilities. This version is affected by these other vulnerabilities: {{ fixed_by_vuln.vulnerability_id }} {{ fixed_by_vuln.vulnerability_id }}
VCID-n7t6-zk51-afc3 Aliases: CVE-2023-37263 GHSA-m284-85mf-cgrc	Strapi's field level permissions not being respected in relationship title ### Summary Field level permissions not being respected in relationship title. If I have a relationship title and the relationship shows a field I don't have permission to see I will still be visible. ### Details No RBAC checks on on the relationship the relation endpoint returns ### PoC #### Setup Create a fresh strapi instance Create a new content type in the newly created content type add a relation to the users-permissions user. Save. Create a users-permissions user Use your created content type and create an entry in it related to the users-permisisons user Go to settings -> Admin panel -> Roles -> Author Give the author role full permissions on the content type your created. Make sure they don't have any permission to see User Save Create a new admin account with only the author role #### CVE login on the newly created author acount. go to the content manager to the colection type you created with the relationship to users_permissions_user You now see a field you don't have permissions to view. ### Impact RBAC field level checks leaks data selected by the admin user as relationship title What could be sensitive fields that they should not be allowed to see. by the person having this specific role.	4.12.1 Affected by 1 other vulnerability. This version is affected by these other vulnerabilities: {{ fixed_by_vuln.vulnerability_id }}

Vulnerability

Summary

Fixed by

VCID-a54s-xn6b-eycd
Aliases:
CVE-2024-29181
GHSA-6j89-frxc-q26m

@strapi/plugin-content-manager leaks data via relations via the Admin Panel 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.

4.19.1
Affected by 0 other vulnerabilities.

VCID-adab-ztym-ayhd
Aliases:
CVE-2023-36472
GHSA-v8gg-4mq2-88q4

Strapi may leak sensitive user information, user reset password, tokens via content-manager views Attackers can get access to user reset password tokens if they have the configure view permissions.

4.11.7
Affected by 2 other vulnerabilities.

VCID-n7t6-zk51-afc3
Aliases:
CVE-2023-37263
GHSA-m284-85mf-cgrc

Strapi's field level permissions not being respected in relationship title ### Summary Field level permissions not being respected in relationship title. If I have a relationship title and the relationship shows a field I don't have permission to see I will still be visible. ### Details No RBAC checks on on the relationship the relation endpoint returns ### PoC #### Setup Create a fresh strapi instance Create a new content type in the newly created content type add a relation to the users-permissions user. Save. Create a users-permissions user Use your created content type and create an entry in it related to the users-permisisons user Go to settings -> Admin panel -> Roles -> Author Give the author role full permissions on the content type your created. Make sure they don't have any permission to see User Save Create a new admin account with only the author role #### CVE login on the newly created author acount. go to the content manager to the colection type you created with the relationship to users_permissions_user You now see a field you don't have permissions to view. ### Impact RBAC field level checks leaks data selected by the admin user as relationship title What could be sensitive fields that they should not be allowed to see. by the person having this specific role.

4.12.1
Affected by 1 other vulnerability.

Vulnerability	Summary	Aliases
This package is not known to fix vulnerabilities.

Vulnerability

Summary

Aliases

This package is not known to fix vulnerabilities.

Date	Actor	Action	Vulnerability	Source	VulnerableCode Version
2026-06-06T05:07:30.077486+00:00	GitLab Importer	Affected by	VCID-a54s-xn6b-eycd	https://gitlab.com/gitlab-org/advisories-community/-/blob/main/npm/@strapi/plugin-content-manager/CVE-2024-29181.yml	38.6.0
2026-06-06T04:06:58.712215+00:00	GitLab Importer	Affected by	VCID-n7t6-zk51-afc3	https://gitlab.com/gitlab-org/advisories-community/-/blob/main/npm/@strapi/plugin-content-manager/CVE-2023-37263.yml	38.6.0
2026-06-06T04:06:55.296994+00:00	GitLab Importer	Affected by	VCID-adab-ztym-ayhd	https://gitlab.com/gitlab-org/advisories-community/-/blob/main/npm/@strapi/plugin-content-manager/CVE-2023-36472.yml	38.6.0