# CVE-2022-39275: Improper object type validation in saleor

> Authenticated users can access unauthorized database objects and expose sensitive user data due to improper ID type validation in GraphQL mutations.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Oct 2022
- **Updated:** 23 Apr 2025
- **Also known as:** GHSA-xhq8-8c5v-w8ff

## What is CVE-2022-39275?

CVE-2022-39275 is a medium-severity missing authorization vulnerability in saleor, published on 6 Oct 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-20 (Improper Input Validation), CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2022-39275?

It affects 1 product.


Products: Saleor Saleor.

## How do I fix CVE-2022-39275?

No fix has been published for CVE-2022-39275 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-39275 being exploited?

There is no known exploitation of CVE-2022-39275 in the wild and no public exploit code.

Public exploit code:

- CVE-2022-39275 Setup and POC (github_poc): https://github.com/omar2535/CVE-2022-39275

## Other vulnerabilities in saleor

- [CVE-2026-24136](https://insights.sbomify.com/CVE-2026-24136/): Saleor has an Insecure Direct Object Reference (IDOR) in GraphQL API (high 8.7)
- [CVE-2026-23499](https://insights.sbomify.com/CVE-2026-23499/): Saleor vulnerable to stored XSS via Unrestricted File Upload (high 8.5)
- [CVE-2026-33756](https://insights.sbomify.com/CVE-2026-33756/): Saleor Affected by Denial of Service via Unbounded GraphQL Query Batching (high 7.5)
- [CVE-2026-35401](https://insights.sbomify.com/CVE-2026-35401/): Saleor has a resource exhaustion vulnerability in GraphQL queries (high 7.5)
- [CVE-2026-22849](https://insights.sbomify.com/CVE-2026-22849/): Saleor lacks proper HTML sanitization in rich text fields (high 7.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-39275 and fix it if it is affected.

What it is: CVE-2022-39275 is a medium-severity missing authorization vulnerability in saleor, published on 6 Oct 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-39275 in the wild and no public exploit code.

Affected product: saleor. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-39275/ (Markdown: https://insights.sbomify.com/CVE-2022-39275/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-39275
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-39275
- OSV: https://osv.dev/vulnerability/CVE-2022-39275

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-39275/
Summaries are generated and may contain mistakes; the official description above is the record.