Saleor is a headless, GraphQL commerce platform. In affected versions some GraphQL mutations were not properly checking the ID type input which allowed to access database objects that the authenticated user may not be allowed to access. This vulnerability can be used to expose the following information: Estimating database row counts from tables with a sequential primary key or Exposing staff user and customer email addresses and full name through the `assignNavigation()` mutation. This issue has been patched in main and backported to multiple releases (3.7.17, 3.6.18, 3.5.23, 3.4.24, 3.3.26, 3.2.14, 3.1.24). Users are advised to upgrade. There are no known workarounds for this issue.
The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.
The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.
| Link | Tags |
|---|---|
| https://github.com/saleor/saleor/security/advisories/GHSA-xhq8-8c5v-w8ff | third party advisory |
| https://github.com/saleor/saleor/commit/96e04c092ddcac17b14f2e31554aa02d9006d0ce | third party advisory patch |