First published: Mon Nov 20 2023(Updated: )
### Impact Users are able to bypass the field level security. This means fields that they where not allowed to populate could be populated anyway even in the event that they tried to populate something that they don't have access to. ### Patches This issue has been patched in 1.3.4 ### Workarounds None
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.
Credit: security-advisories@github.com security-advisories@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
npm/strapi-plugin-protected-populate | <1.3.4 | 1.3.4 |
Strapi Protected Populate | <1.3.4 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The vulnerability ID is CVE-2023-48218.
CVE-2023-48218 has a severity keyword of 'medium' and a severity value of 5.3.
CVE-2023-48218 affects the Strapi Protected Populate Plugin prior to version 1.3.4.
To fix CVE-2023-48218, update the Strapi Protected Populate Plugin to version 1.3.4 or later.
The CWE ID for CVE-2023-48218 is 863.