EUVD-2026-188111

fkie_cve-2023-37263

Strapi is the an open-source headless content management system. Prior to version 4.12.1, field level permissions are not respected in the relationship title. If an actor has relationship title and the relationship shows a field they don't have permission to see, the field will still be visible. Version 4.12.1 has a fix for this issue.

GHSA-m284-85mf-cgrc — Strapi's field level permissions not being respected in relationship title

Affected: npm: @strapi/plugin-content-manager

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

Most recent entries from all

EUVD-2026-188111

fkie_cve-2023-37263

GHSA-m284-85mf-cgrc — Strapi's field level permissions not being respected in relationship title

gsd-2023-37263