Skip to content
Connect AISign inSign up free
CVE-2026-444728.1HighCWE-287

CVE-2026-44472: Saleor: Account pre-hijacking vulnerability due to unverified anonymous order merge

saleor

Affected: saleor · Exploitation: unlikely (under 1%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

0.6%probability of exploitation in the next 30 days
50th percentile
050100

Higher than 50% of scored CVEs

8.1HighCVSS 3.1
LowHigh

DescriptionCVE.org

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.

Affected products1

From the CVE record. A product or version that is not listed is unknown, not unaffected.

  • saleor · saleor>= 2.10.0rc1, < 3.21.67; >= 3.22.0-a.0, < 3.22.63; >= 3.23.0-a.0, < 3.23.22

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas
Exploitation
Unlikely (under 1%). EPSS under 1%, or no score yet.
CISA KEV
Not listed
Public check
No public nuclei template
Vendor
saleor
Published
August 2026

CoverageNo articles yet

No CyberSIXT article names CVE-2026-44472 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.

References