CVE-2022-39275

Improper object type validation in saleor

MEDIUM
4.3
CVSS Score
Published: October 6, 2022 at 12:00 AM UTC
Updated: June 17, 2026 at 04:58 AM UTC
1 product affected across 1 vendorSaleor

Using saleor by saleor?

Get instant alerts when new vulnerabilities affect saleor - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM4.3
Exploit prediction
EPSS 0.8%
SSVC
No known exploit

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

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 3.1.24v < 3.2.14v < 3.3.26v < 3.4.24v < 3.5.23v < 3.6.18v < 3.7.172.0.0 ≤ v < 3.1.243.2.0 ≤ v < 3.2.143.3.0 ≤ v < 3.3.263.4.0 ≤ v < 3.4.243.5.0 ≤ v < 3.5.233.6.0 ≤ v < 3.6.183.7.0 ≤ v < 3.7.17
Affected range stops below 3.1.24, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.2.14, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.3.26, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.4.24, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.5.23, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.6.18, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.7.17, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

SSVC — Action Prioritization

SSVCNo known exploitAutomatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
NETWORK
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
LOW
Integrity
NONE
Availability
NONE
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-863CWE-20

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card