Strapi Protected Populate Plugin leaking fields if the request fields where empty or only fields selected where not populatable
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| strapi-community | strapi-plugin-protected-populate | affected |
|
No data.
No data available yet.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2023-2899 | 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. |
Github GHSA |
GHSA-6h67-934r-82g7 | Bypass of field access control in strapi-plugin-protected-populate |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.601% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.