CVE-2023-48218: Strapi Protected Populate Plugin leaking fields if the request fields where empty or only fields selected where not populatable
First published: Mon Nov 20 2023(Updated: )
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.
This issue has been patched in 1.3.4
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: firstname.lastname@example.org email@example.com
|Affected Software||Affected Version||How to fix|
|Strapi Protected Populate||<1.3.4|
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Frequently Asked Questions
What is the vulnerability ID?
The vulnerability ID is CVE-2023-48218.
What is the severity of CVE-2023-48218?
CVE-2023-48218 has a severity keyword of 'medium' and a severity value of 5.3.
How does CVE-2023-48218 affect the software?
CVE-2023-48218 affects the Strapi Protected Populate Plugin prior to version 1.3.4.
How can I fix CVE-2023-48218?
To fix CVE-2023-48218, update the Strapi Protected Populate Plugin to version 1.3.4 or later.
What is the Common Weakness Enumeration (CWE) ID for CVE-2023-48218?
The CWE ID for CVE-2023-48218 is 863.
- product/protected populate
- canonical/strapi protected populate
SecAlerts Pty Ltd.
132 Wickham Terrace
QLD 4006, Australiainfo@secalerts.co
© 2023 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203