How severe is GHSA-6j89-frxc-q26m?

GHSA-6j89-frxc-q26m has a CVSS score of 2.3/10, rated LOW. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-6j89-frxc-q26m?

GHSA-6j89-frxc-q26m affects the following packages: @strapi/plugin-content-manager (npm). Ecosystems affected: npm.

How do I fix GHSA-6j89-frxc-q26m?

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.

How do I detect GHSA-6j89-frxc-q26m in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @strapi/plugin-content-manager. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-6j89-frxc-q26m if there is no patch (or I can't update yet)?

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 does O3 Security protect against GHSA-6j89-frxc-q26m?

O3 pinpoints whether GHSA-6j89-frxc-q26m is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-6j89-frxc-q26m actively exploited in the wild?

Yes. There are 1 known exploit references for GHSA-6j89-frxc-q26m, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for GHSA-6j89-frxc-q26m?

GHSA-6j89-frxc-q26m has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 30th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-6j89-frxc-q26m?

GHSA-6j89-frxc-q26m is classified as CWE-639 (CWE-639). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-6j89-frxc-q26m published, and has it been updated?

GHSA-6j89-frxc-q26m was published on June 12, 2024 and was last updated on June 12, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

GHSA-6j89-frxc-q26m

LOW

@strapi/plugin-content-manager leaks data via relations via the Admin Panel

Also known asCVE-2024-29181

Published

Jun 12, 2024

Updated

Jun 12, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk30th percentile-0.05%

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.

Blast Radius

1 pkg affected

Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.

@strapi/plugin-content-managernpm

74Kdownloads / week

Description

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

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@strapi/plugin-content-manager`	all versions	4.19.1

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Strapi is an open-source content management system. Prior to version 4.1…

github.comNVDSep 2024

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @strapi/plugin-content-manager. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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 pinpoints whether GHSA-6j89-frxc-q26m is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

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

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

O3 Security · Impact-Aware SCA

Is GHSA-6j89-frxc-q26m in your dependencies?

O3 detects GHSA-6j89-frxc-q26m across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works