GHSA-6h67-934r-82g7 — strapi-plugin-protected-p…
MEDIUMFix: strapi-community/strapi-plugin-protected-populate@0544106GHSA-6h67-934r-82g7 is a medium-severity (CVSS 5.3) CWE-863 vulnerability in strapi-plugin-protected-populate. A fix is available for strapi-plugin-protected-populate — see the affected versions and patch details below.
Bypass of field access control in strapi-plugin-protected-populate
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-6h67-934r-82g7 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 379,145 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-protected-populatenpmDescription
The Strapi Protected Populate Plugin protects get endpoints from revealing too much information. Prior to version 1.3.4, users were able to bypass the field level security. Users who tried to populate something that they didn't have access to could populate those fields anyway. This issue has been patched in version 1.3.4. There are no known workarounds.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | strapi-plugin-protected-populate | all versions | 1.3.4npm install strapi-plugin-protected-populate@1.3.4 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for strapi-plugin-protected-populate, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update strapi-plugin-protected-populate to 1.3.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6h67-934r-82g7 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-6h67-934r-82g7 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-6h67-934r-82g7. 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-6h67-934r-82g7 in your dependencies?
O3 Security finds GHSA-6h67-934r-82g7 across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.