Strapi's field level permissions not being respected in relationship titleGHSA-m284-85mf-cgrc
MEDIUMGHSA-m284-85mf-cgrc is a medium-severity (CVSS 6.8) Information Exposure vulnerability in @strapi/plugin-content-manager. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for @strapi/plugin-content-manager — see the affected versions and patch details below.
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
Exploitation and automatability from CISA’s SSVC triage for GHSA-m284-85mf-cgrc.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
@strapi/plugin-content-managernpmDescription
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @strapi/plugin-content-manager | all versions | 4.12.1npm install @strapi/plugin-content-manager@4.12.1 |
Affected Products
strapistrapiResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @strapi/plugin-content-manager, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @strapi/plugin-content-manager to 4.12.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m284-85mf-cgrc is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.
Frequently Asked Questions
Is GHSA-m284-85mf-cgrc in your dependencies?
Find it across npm, including transitive dependencies.