{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-35407 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-35407 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-35407 is a medium-severity vulnerability in saleor, published on 8 Apr 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-35407 and fix it if it is affected.\n\nWhat it is: CVE-2026-35407 is a medium-severity vulnerability in saleor, published on 8 Apr 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-35407 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-2026-35407/ (Markdown: https://insights.sbomify.com/CVE-2026-35407/index.md)","id":"CVE-2026-35407","markdown":"https://insights.sbomify.com/CVE-2026-35407/index.md","name":"CVE-2026-35407","record":{"aliases":["GHSA-hwph-9537-mc3p"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["account_takeover","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Saleor e-commerce platform","requires_auth":"low_privilege","summary":"Attackers can change email addresses on other user accounts by replaying confirmation tokens, leading to account takeover.","user_interaction":"required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"saleor","vendor":"saleor"}],"cvss":{"score":5.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:P/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-285","name":"Improper Authorization"}],"description":"Saleor is an e-commerce platform. From 2.10.0 to before 3.23.0a3, 3.22.47, 3.21.54, and 3.20.118, a business-logic and authorization flaw was found in the account email change workflow, the confirmation flow did not verify that the email change confirmation token was issued for the given authenticated user. As a result, a valid email-change token generated for one account can be replayed while authenticated as a different account. The second account’s email address is then updated to the token's new_email, even though that token was never issued for that account. This vulnerability is fixed in 3.23.0a3, 3.22.47, 3.21.54, and 3.20.118.","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 has Cross-Account Email Change via Unbound Confirmation Token","id":"CVE-2026-35407","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"business_logic","year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"Directus is Missing Cross-Origin Opener Policy","id":"CVE-2026-35408"},"packages":[],"prev":{"headline":"Aardvark-dns has incorrect error handling for malformed tcp packets","id":"CVE-2026-35406"},"products":["saleor"],"published":"2026-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":"2026-04-10","vendors":["saleor"]},"summary":"Attackers can change email addresses on other user accounts by replaying confirmation tokens, leading to account takeover.","url":"https://insights.sbomify.com/CVE-2026-35407/"}