{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-31205 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-31205 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2024-31205 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2024-31205 in the wild and no public exploit code.\n\nAffected product: saleor. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2024-31205/ (Markdown: https://insights.sbomify.com/CVE-2024-31205/index.md)","id":"CVE-2024-31205","markdown":"https://insights.sbomify.com/CVE-2024-31205/index.md","name":"CVE-2024-31205","record":{"aliases":["GHSA-ff69-fwjf-3c9w"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Saleor e-commerce platform","requires_auth":"none","summary":"Attackers can bypass CSRF validation in the refreshToken mutation to obtain valid access tokens, potentially leading to account takeover.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"saleor","vendor":"saleor"}],"cvss":{"score":4.2,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"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`.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Saleor CSRF bypass in refreshToken mutation","id":"CVE-2024-31205","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2024"},"n_packages":0,"n_references":2,"next":{"headline":"Use of Unencrypted HTTP Request in dectalk-tts","id":"CVE-2024-31206"},"packages":[],"prev":{"headline":"mailcow Cross-site Scripting Vulnerability via Exception Handler","id":"CVE-2024-31204"},"products":["saleor"],"published":"2024-04-08","related":[{"cvss_score":8.7,"headline":"Saleor has an Insecure Direct Object Reference (IDOR) in GraphQL API","id":"CVE-2026-24136","kev_date_added":null,"published":"2026-01-23"},{"cvss_score":8.5,"headline":"Saleor vulnerable to stored XSS via Unrestricted File Upload","id":"CVE-2026-23499","kev_date_added":null,"published":"2026-01-21"},{"cvss_score":7.5,"headline":"Saleor Affected by Denial of Service via Unbounded GraphQL Query Batching","id":"CVE-2026-33756","kev_date_added":null,"published":"2026-04-08"},{"cvss_score":7.5,"headline":"Saleor has a resource exhaustion vulnerability in GraphQL queries","id":"CVE-2026-35401","kev_date_added":null,"published":"2026-04-08"},{"cvss_score":7.2,"headline":"Saleor lacks proper HTML sanitization in rich text fields","id":"CVE-2026-22849","kev_date_added":null,"published":"2026-01-21"},{"cvss_score":6.5,"headline":"Saleor is vulnerable to staff-authenticated error message information disclosure vulnerability via Python exceptions","id":"CVE-2023-26051","kev_date_added":null,"published":"2023-03-02"},{"cvss_score":6.5,"headline":"Missing Authorization in saleor/saleor","id":"CVE-2022-0932","kev_date_added":null,"published":"2022-03-11"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-08-02","vendors":["saleor"]},"summary":"Attackers can bypass CSRF validation in the refreshToken mutation to obtain valid access tokens, potentially leading to account takeover.","url":"https://insights.sbomify.com/CVE-2024-31205/"}