Read the docs
TI-2026-32411 Aliases CVE-2026-44472

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

Priority LOW 38CWE-287Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
Required
Attack complexity
Low
Impact type
Security bypass
Confidentiality · integrity · availability
High · High · None
Fix status
Fixed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-287.

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.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.0063 50th percentileScored 2026-11-07
Fix Fixed saleor (saleor): 3.21.67, 3.22.63, 3.23.22

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Total

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
saleorsaleor2.10.0rc1 to before 3.21.67; 3.22.0-a.0 to before 3.22.63; 3.23.0-a.0 to before 3.23.223.21.67, 3.22.63, 3.23.22Patch availableCNA
  • saleor Vendorsaleor Affected 2.10.0rc1 to before 3.21.67; 3.22.0-a.0 to before 3.22.63; 3.23.0-a.0 to before 3.23.22 Fixed in 3.21.67, 3.22.63, 3.23.22 Patch available CNA

CPE names Threatist (inferred) · 1

Inferred from how NVD named this product before; not given by a source.

CPEVersionsRoleVendor
cpe:2.3:a:saleor:saleor:*:*:*:*:*:*:*:*——saleor
  • cpe:2.3:a:saleor:saleor:*:*:*:*:*:*:*:* Versions — — ·saleor

Remediation

  • Fix · CNA saleor (saleor) Fixed in 3.21.67, 3.22.63, 3.23.22

Timeline

  1. 2026-10-02 Threatist record created from CVE-2026-44472
  2. 2026-10-28 EPSS moved to the 50th–90th percentile

References

  • TI-2026-19454 Saleor has an Insecure Direct Object Reference (IDOR) in GraphQL API CVSS 4.0HIGH 8.7
  • TI-2026-27537 Saleor has a resource exhaustion vulnerability in GraphQL queries CVSS 3.1HIGH 7.5
  • TI-2026-26135 Saleor Affected by Denial of Service via Unbounded GraphQL Query Batching CVSS 3.1HIGH 7.5
  • TI-2026-18932 Saleor vulnerable to stored XSS via Unrestricted File Upload CVSS 4.0HIGH 8.5
  • TI-2026-36015 Saleor: Anonymous users can modify channel settings via `channelUpdate` due to `all([])` bypass in permission check CVSS 3.1MEDIUM 6.5
  • TI-2026-18341 Saleor lacks proper HTML sanitization in rich text fields CVSS 4.0HIGH 7.2
See all 20 →

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences