# CVE-2024-31205: Saleor CSRF bypass in refreshToken mutation

> Attackers can bypass CSRF validation in the refreshToken mutation to obtain valid access tokens, potentially leading to account takeover.

- **Severity:** Medium 4.2 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 8 Apr 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-ff69-fwjf-3c9w

## What is CVE-2024-31205?

CVE-2024-31205 is a medium-severity vulnerability in saleor, published on 8 Apr 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Saleor is an e-commerce platform. Starting in version 3.10.0 and prior to versions 3.14.64, 3.15.39, 3.16.39, 3.17.35, 3.18.31, and 3.19.19, an attacker may bypass cross-set request forgery (CSRF) validation when calling refresh token mutation with empty string. When a user provides an empty string in `refreshToken` mutation, while the token persists in `JWT_REFRESH_TOKEN_COOKIE_NAME` cookie, application omits validation against CSRF token and returns valid access token. Versions 3.14.64, 3.15.39, 3.16.39, 3.17.35, 3.18.31, and 3.19.19 contain a patch for the issue. As a workaround, one may replace `saleor.graphql.account.mutations.authentication.refresh_token.py.get_refresh_token`. This will fix the issue, but be aware, that it returns `JWT_MISSING_TOKEN` instead of `JWT_INVALID_TOKEN`.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2024-31205?

It affects 1 product.


Products: Saleor Saleor.

## How do I fix CVE-2024-31205?

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

## Is CVE-2024-31205 being exploited?

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

## 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-2024-31205 and fix it if it is affected.

What it is: CVE-2024-31205 is a medium-severity vulnerability in saleor, published on 8 Apr 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-31205 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-2024-31205/ (Markdown: https://insights.sbomify.com/CVE-2024-31205/index.md)
```

## Sources

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

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