CVE-2026-44472 json
Saleor: Account pre-hijacking vulnerability due to unverified anonymous order merge
published 2026-08-18 2 mo ago modified 2026-09-18 51 d ago also EUVD-2026-61069
- cvss
- 8.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 50%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- saleor saleor 3.21.67, 3.22.63, 3.23.22
- github.com/saleor/saleor@299cdfb commit
- github.com/saleor/saleor@4251672 commit
- github.com/saleor/saleor@5110542 commit
- github.com/saleor/saleor@dc63e42 commit
- github.com/saleor/saleor/releases/tag/3.21.67 release
- github.com/saleor/saleor/releases/tag/3.22.63 release
- github.com/saleor/saleor/releases/tag/3.23.22 release
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 2 mo ago
Exploit prediction
0.63% chance of exploitation in the next 30 days, higher than 50% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N |
Affected products
- saleor saleor
Classification
- Weakness
-
- CWE-287 Improper Authentication
References
- github.com /saleor/saleor/commit/299cdfb1a5737108b78b5c2c0d29b94f3b7331a2
- github.com /saleor/saleor/commit/42516727823cb74cb6b875070956debecf9ffdb8
- github.com /saleor/saleor/commit/5110542c164991384fa3c4f01983e8c76823ce0f
- github.com /saleor/saleor/commit/dc63e422afc9f6ce115d75f045886b01b4f13e2b
- github.com /saleor/saleor/security/advisories/GHSA-6whj-8p3f-2xqp
- github.com /saleor/saleor/releases/tag/3.21.67
- github.com /saleor/saleor/releases/tag/3.22.63
- github.com /saleor/saleor/releases/tag/3.23.22
Sources
- CVE List CVE-2026-44472
- NVD CVE-2026-44472
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.