{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-93650 exists.","fix":"No fix has been published for CVE-2026-93650 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-93650 is a medium-severity vulnerability in Saleor, published on 18 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-93650 and fix it if it is affected.\n\nWhat it is: CVE-2026-93650 is a medium-severity vulnerability in Saleor, published on 18 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-93650 exists.\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-2026-93650/ (Markdown: https://insights.sbomify.com/CVE-2026-93650/index.md)","id":"CVE-2026-93650","markdown":"https://insights.sbomify.com/CVE-2026-93650/index.md","name":"CVE-2026-93650","record":{"aliases":["GHSA-6276-frvw-567j"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"E-commerce platform","requires_auth":"none","summary":"Attackers can bypass authentication throttling by spoofing IP addresses if the application is not configured to trust specific proxy headers.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P","version":"4.0"},"cwes":[{"id":"CWE-799","name":"Improper Control of Interaction Frequency"},{"id":"CWE-307","name":"Improper Restriction of Excessive Authentication Attempts"}],"description":"A vulnerability was determined in Saleor up to 3.20.118/3.21.54/3.22.47/3.23.14. This vulnerability affects the function get_client_ip of the file saleor/account/throttling.py. Executing a manipulation can lead to improper restriction of excessive authentication attempts. The attack can be executed remotely. The attack requires a high level of complexity. It is stated that the exploitability is difficult. The exploit has been publicly disclosed and may be utilized. The projects own issue #19203 internal ticket admits \"IP can be spoofed in most deployments\" and that its REAL_IP_ENVIRON-type setting bypasses get_client_ip; fix (right-to-left RFC 7239 hop selection) proposed but still unmerged. The vendor explains within an email, that \"[t]his is not a vulnerability, this is working at intended, Saleor expects XFF to be configured properly\".","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Saleor throttling.py get_client_ip excessive authentication","id":"CVE-2026-93650","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":0,"n_references":7,"next":{"headline":"WordPress Minimum and Maximum Quantity for WooCommerce plugin \u003c= 2.1.2 - PHP Object Injection vulnerability","id":"CVE-2026-93651"},"packages":[],"prev":{"headline":"Open redirect in Adoptium Temurin","id":"CVE-2026-93649"},"products":["Saleor"],"published":"2026-09-18","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-18","vendors":["n/a"]},"summary":"Attackers can bypass authentication throttling by spoofing IP addresses if the application is not configured to trust specific proxy headers.","url":"https://insights.sbomify.com/CVE-2026-93650/"}