GHSA-6j89-frxc-q26m is a low-severity (CVSS 2.3) CWE-639 vulnerability in @strapi/plugin-content-manager. 1 public exploit reference exists, so weaponization risk is real. A fix is available for @strapi/plugin-content-manager — see the affected versions and patch details below.
@strapi/plugin-content-manager leaks data via relations via the Admin Panel
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-6j89-frxc-q26m.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
GHSA-6j89-frxc-q26m plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,636 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
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
- 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
- Sign in as Admin. Navigate to content creation.
- Select a collection and verify you have items you created there. And that they have associations to other protected collections.
- Verify role permissions for your collections are set to CRUD if user created.
- Log out and sign in as a unrelated Author.
- Navigate to content management and verify you see collections built by admin but empty for you (as expected)
- Create a new item as an Author and see the card appear with attributes to fill out.
- Use the form pull down for the associations.
- 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
Good at top level no items seen
Drop down in Author login can see Admin data
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @strapi/plugin-content-manager | all versions | 4.19.1npm install @strapi/plugin-content-manager@4.19.1 |
Research 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.19.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6j89-frxc-q26m is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-6j89-frxc-q26m can be triaged on real exposure rather than presence alone.
Tailored to GHSA-6j89-frxc-q26m. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-6j89-frxc-q26m in your dependencies?
O3 Security finds GHSA-6j89-frxc-q26m across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.