GHSA-chmr-rg2f-9jmf
MEDIUMMaking all attributes on a content-type public without noticing it
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.
Blast Radius
Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.
@strapi/strapinpmDescription
Summary
Anyone (Strapi developers, users, plugins) can make every attribute of a Content-Type public without knowing it.
Details
When dealing with content-types inside a Strapi instance, we can extend those using the appropriate container:
strapi.container.get('content-types').extend(contentTypeUID, (contentType) => newContentType);
The vulnerability only affects the handling of content types by Strapi, not the actual content types themselves. Users can use plugins or modify their own content types without realizing that the privateAttributes getter is being removed, which can result in any attribute becoming public. This can lead to sensitive information being exposed or the entire system being taken control of by an attacker(having access to password hashes).
PoC
Extend any content type on runtime (like in the bootstrap functions) and do a copy of the content-type object.
strapi.container.get('content-types').extend(contentTypeUID, (contentType) => {
const newCT = { ... contentType, attributes: { ...contentType.attributes, newAttr: {} } };
return newCT;
});
This will have as effect to remove the getter and as we rely on it in sanitization, every attributes will be considered as public.
Impact
Everyone can be impacted. Depending on how people are using/extending content-types. If the users are mutating the content-type, they will not be affected.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @strapi/strapi | all versions | 4.10.8 |
| 📦npm | @strapi/utils | all versions | 4.10.8 |
| 📦npm | @strapi/database | all versions | 4.10.8 |
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/strapi. 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/strapi to 4.10.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-chmr-rg2f-9jmf 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-chmr-rg2f-9jmf 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-chmr-rg2f-9jmf. 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-chmr-rg2f-9jmf in your dependencies?
O3 detects GHSA-chmr-rg2f-9jmf across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.