CVE-2024-31205

Severity CVSS v4.0:
Pending analysis
Type:
CWE-352 Cross-Site Request Forgery (CSRF)
Publication date:
08/04/2024
Last modified:
07/01/2026

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`.<br />

Vulnerable products and versions

CPE From Up to
cpe:2.3:a:saleor:saleor:*:*:*:*:*:*:*:* 3.10.0 (including) 3.14.64 (excluding)
cpe:2.3:a:saleor:saleor:*:*:*:*:*:*:*:* 3.15.0 (including) 3.15.39 (excluding)
cpe:2.3:a:saleor:saleor:*:*:*:*:*:*:*:* 3.16.0 (including) 3.16.39 (excluding)
cpe:2.3:a:saleor:saleor:*:*:*:*:*:*:*:* 3.17.0 (including) 3.17.35 (excluding)
cpe:2.3:a:saleor:saleor:*:*:*:*:*:*:*:* 3.18.0 (including) 3.18.31 (excluding)
cpe:2.3:a:saleor:saleor:*:*:*:*:*:*:*:* 3.19.0 (including) 3.19.19 (excluding)