saleor: Improper Authentication
CVE-2026-44472 is a high-severity improper authentication vulnerability in saleor, with a CVSS 3.1 base score of 8.1 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, but only if a user takes part, for example by opening a link or file. Affected saleor versions: >= 2.10.0rc1, < 3.21.67; >= 3.22.0-a.0, < 3.22.63; >= 3.23.0-a.0, < 3.23.22. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.63% chance of exploitation within 30 days, higher than 51% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Check which version of saleor you run against the affected versions below, and install the vendor's latest release.
- Read the advisory on github.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
- Because the attack needs a user to take part, warn users about unexpected links and files related to this product until it is patched.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Saleor | saleor | >= 2.10.0rc1, < 3.21.67; >= 3.22.0-a.0, < 3.22.63; >= 3.23.0-a.0, < 3.23.22 | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- RequiredA user must take an action such as opening a file or link.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N. Scored by CNA (github.com).
Official description
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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Authentication
When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.
How developers prevent this class of flaw
- Use an authentication framework or library such as the OWASP ESAPI Authentication feature.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
- 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/releases/tag/3.21.67
- github.com/saleor/saleor/releases/tag/3.22.63
- github.com/saleor/saleor/releases/tag/3.23.22
Other vulnerabilities in saleor
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
Recent Improper Authentication vulnerabilities
- 7.6 High severity
- 8.8 High severity
- 8.8 High severity
- 8.8 High severity
- 8.8 High severity
- 9.8 Critical severity
Spotted an error? Tell us.