CVE-2026-44472
HighCVSS 8.1Exploitation Probability (EPSS)
Low risk37th percentile - higher than 37% 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.
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.