CVE-2023-48218: Strapi Protected Populate Plugin leaking fields if the request fields where empty or only fields selected where not populatable
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
Other sources
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 Software
Remediation
Event History
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.