Skip to content
OpenAdvisories
Medium · 5.3 Public exploit CVE-2022-39275 EUVD-2022-41779

Improper object type validation in saleor

Published Oct 6, 2022 · Updated Apr 23, 2025 · Assigned by GitHub_M

Description

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.

Affected products

VendorProductAffectedFixed
saleor saleor >= 2.0.0, < 3.1.24, >= 3.2.0, < 3.2.14, >= 3.3.0, < 3.3.26, >= 3.4.0, < 3.4.24, >= 3.5.0, < 3.5.23, >= 3.6.0, < 3.6.18, >= 3.7.0, < 3.7.17 —

Public exploits

Exploit or proof-of-concept code for this vulnerability is publicly available, which lowers the bar for attackers. Treat it as a reason to patch sooner.

Third-party code, not reviewed by us. Public PoCs are sometimes fake or contain malware. Read the code first and run it only in an isolated lab, against systems you are authorised to test.

GitHub 1 repository

Sources: PoC-in-GitHub, Metasploit Framework, Exploit-DB — updated daily. Only links are listed; no exploit code is hosted here.

References