CVE-2026-44472
HighCVSS 8.1Exploitation Probability (EPSS)
Low risk38th percentile - higher than 38% of all known CVEs
Summary
Saleor from version 2.10.0rc1 to 3.21.67, 3.22.63, and 3.23.22 treats email verification as sufficient proof of account ownership and automatically associates anonymous commerce data with the newly activated account. An attacker can create an account with the victim's email address, and after the victim activates it, gain access to their order history and personal data.
Risk Assessment
The organization is exposed to customer privacy breaches, as an attacker can take over the victim's order history and personal data, potentially leading to identity theft and data protection regulation violations.
Recommendation
It is recommended to upgrade Saleor to version 3.21.67, 3.22.63, or 3.23.22 (or later) and enable password confirmation before merging anonymous data.
Other vulnerabilities in Saleor
See all- CVE-2026-93650Low
In Saleor up to 3.20.118/3.21.54/3.22.47/3.23.14, the get_client_ip function in saleor/account/throttling.py allows bypassing authentication attempt throttling by spoofing the client IP. The vendor considers this intended behavior, stating that XFF should be configured properly. The exploit has been publicly disclosed.
- CVE-2026-48744Medium
Saleor versions from 3.14.67 to 3.21.67, 3.22.63, and 3.23.22 have a broken authorization check in saleor/permission/utils.py that can incorrectly authorize unauthenticated GraphQL requests. This allows anonymous callers to use the channelUpdate() mutation to change channel order settings such as allowUnpaidOrders even when the response reports PermissionDenied. The same permission utility can expose hidden objects through pageType() and translation() queries, including attributes with visibleInStorefront set to false.
- CVE-2026-39851Medium
Saleor, an e-commerce platform, from version 2.10.0 to before 3.23.0a3, 3.22.47, 3.21.54, and 3.20.118, has a vulnerability in the requestEmailChange() mutation that revealed the existence of user-provided email addresses in error messages. This is fixed in versions 3.23.0a3, 3.22.47, 3.21.54, and 3.20.118.
- CVE-2026-35407Medium
Saleor from 2.10.0 to before 3.23.0a3, 3.22.47, 3.21.54, and 3.20.118 has a business-logic and authorization flaw in the email change workflow. An email change token generated for one account can be replayed while authenticated as a different account, changing the second account's email to the token's new_email.
- CVE-2026-35401High
Saleor is an e-commerce platform. From 2.0.0 to before 3.23.0a3, 3.22.47, 3.21.54, and 3.20.118, a malicious actor can include many GraphQL mutations or queries in a single API call using aliases or chaining multiple mutations, resulting in resource exhaustion. This vulnerability is fixed in 3.23.0a3, 3.22.47, 3.21.54, and 3.20.118.
- CVE-2026-33756High
Saleor from version 2.0.0 to before 3.23.0a3, 3.22.47, 3.21.54, and 3.20.118 supports GraphQL query batching without limiting the number of operations. An unauthenticated attacker can send a single HTTP request with many operations, bypassing the per-query complexity limit.
Original NVD description (English source)
Saleor is an e-commerce platform. From 2.10.0rc1 until 3.21.67, 3.22.63, and 3.23.22, the account activation flow treats email verification as sufficient proof of account ownership and automatically associates anonymous commerce data with the newly activated account. An attacker can use accountRegister to create an account with a victim's email address before the victim registers. If the victim follows the activation link sent to that mailbox, Saleor activates the attacker-created account and saleor/graphql/account/mutations/account/confirm_account.py can merge anonymous orders and gift-card data for the same email address without requiring the account password or another authentication factor. The attacker can then access the merged order history and personal data, including names, addresses, and phone numbers. The patched supported lines disable automatic merging by default, while the redesigned 3.24.0 flow requires password confirmation before anonymous objects are linked. This issue is fixed in versions 3.21.67, 3.22.63, and 3.23.22.
Vulnerability data from NVD (NIST) · CISA KEV · EPSS