{"answers":{"affected":"3 open source packages ship an affected version, including saleor. It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-13594 in the wild and no public exploit code.","fix":"Upgrade saleor to 2.8.0 or later.","what":"CVE-2019-13594 is a high-severity vulnerability in n/a, published on 14 Jul 2019. 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-2019-13594 and fix it if it is affected.\n\nWhat it is: CVE-2019-13594 is a high-severity vulnerability in n/a, published on 14 Jul 2019. 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-2019-13594 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- saleor (PyPI): affected from 2.7.0; fixed in 2.8.0\n- saleor (PyPI): affected from 2.7.0; fixed in 2.8.0\n- saleor (PyPI): affected from 2.7.0; fixed in 2.8.0\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-2019-13594/ (Markdown: https://insights.sbomify.com/CVE-2019-13594/index.md)","id":"CVE-2019-13594","markdown":"https://insights.sbomify.com/CVE-2019-13594/index.md","name":"CVE-2019-13594","record":{"aliases":["GHSA-fgjh-x3f8-8gmh","PYSEC-2026-916"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Saleor e-commerce platform","requires_auth":"none","summary":"Attackers can perform unauthorized actions on behalf of users because CSRF protection was disabled in Saleor.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"saleor","vendor":"mirumee"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"In Mirumee Saleor 2.7.0 (fixed in 2.8.0), CSRF protection middleware was accidentally disabled, which allowed attackers to send a POST request without a valid CSRF token and be accepted by the server.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Mirumee Saleor CSRF Protection Disabled","id":"CVE-2019-13594","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"csrf","year":"2019"},"n_packages":3,"n_references":1,"next":{"headline":"Command injection in n/a","id":"CVE-2019-13597"},"packages":[{"ecosystem":"PyPI","fixed":["2.8.0"],"introduced":["2.7.0"],"last_affected":[],"package":"saleor","purl":null,"source":"GHSA-fgjh-x3f8-8gmh"},{"ecosystem":"PyPI","fixed":["2.8.0"],"introduced":["2.7.0"],"last_affected":[],"package":"saleor","purl":"pkg:pypi/saleor","source":"GHSA-fgjh-x3f8-8gmh"},{"ecosystem":"PyPI","fixed":["2.8.0"],"introduced":["2.7.0"],"last_affected":[],"package":"saleor","purl":"pkg:pypi/saleor","source":"PYSEC-2026-916"}],"prev":{"headline":"Null dereference in n/a","id":"CVE-2019-13590"},"products":["n/a"],"published":"2019-07-14","related":[{"cvss_score":6.9,"headline":"Client caching login operation with plaintext password in Saleor Storefront","id":"CVE-2020-15085","kev_date_added":null,"published":"2020-06-30"},{"cvss_score":5.3,"headline":"Missing Authentication for Critical Function in Saleor","id":"CVE-2020-7964","kev_date_added":null,"published":"2020-01-24"},{"cvss_score":5.3,"headline":"Missing authorization in Saleor","id":"CVE-2019-1010304","kev_date_added":null,"published":"2019-07-15"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Attackers can perform unauthorized actions on behalf of users because CSRF protection was disabled in Saleor.","url":"https://insights.sbomify.com/CVE-2019-13594/"}