Saleor has Cross-Account Email Change via Unbound Confirmation Token
Key facts
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- Passive
- Attack complexity
- High
- Attack requirements
- Present
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- None · High · None
- Fix status
- Fixed
Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-285.
Summary
Saleor is an e-commerce platform. From 2.10.0 to before 3.23.0a3, 3.22.47, 3.21.54, and 3.20.118, a business-logic and authorization flaw was found in the account email change workflow, the confirmation flow did not verify that the email change confirmation token was issued for the given authenticated user. As a result, a valid email-change token generated for one account can be replayed while authenticated as a different account. The second account’s email address is then updated to the token's new_email, even though that token was never issued for that account. This vulnerability is fixed in 3.23.0a3, 3.22.47, 3.21.54, and 3.20.118.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| saleor | saleor | 2.10.0 to before 3.20.118; 3.21.0-a.0 to before 3.21.54; 3.22.0-a.0 to before 3.22.47; 3.23.0-a.0 to before 3.23.0a3 | 3.20.118, 3.21.54, 3.22.47, 3.23.0a3 | Patch available | CNA |
- saleor Vendorsaleor Affected 2.10.0 to before 3.20.118; 3.21.0-a.0 to before 3.21.54; 3.22.0-a.0 to before 3.22.47; 3.23.0-a.0 to before 3.23.0a3 Fixed in 3.20.118, 3.21.54, 3.22.47, 3.23.0a3 Patch available CNA
CPE configurations NVD · 5
| CPE | Versions | Role | Vendor |
|---|---|---|---|
| cpe:2.3:a:saleor:saleor:*:*:*:*:*:*:*:* | 2.10.0 to before 3.20.118; 3.20.119 to before 3.21.54; 3.22.0 to before 3.22.47 | Vulnerable | saleor |
| cpe:2.3:a:saleor:saleor:3.23.0:*:*:*:*:*:*:* | 3.23.0 | Vulnerable | saleor |
| cpe:2.3:a:saleor:saleor:3.23.0:a0:*:*:*:*:*:* | 3.23.0 a0 | Vulnerable | saleor |
| cpe:2.3:a:saleor:saleor:3.23.0:a1:*:*:*:*:*:* | 3.23.0 a1 | Vulnerable | saleor |
| cpe:2.3:a:saleor:saleor:3.23.0:a2:*:*:*:*:*:* | 3.23.0 a2 | Vulnerable | saleor |
- cpe:2.3:a:saleor:saleor:*:*:*:*:*:*:*:* Versions 2.10.0 to before 3.20.118; 3.20.119 to before 3.21.54; 3.22.0 to before 3.22.47 Vulnerable ·saleor
- cpe:2.3:a:saleor:saleor:3.23.0:*:*:*:*:*:*:* Versions 3.23.0 Vulnerable ·saleor
- cpe:2.3:a:saleor:saleor:3.23.0:a0:*:*:*:*:*:* Versions 3.23.0 a0 Vulnerable ·saleor
- cpe:2.3:a:saleor:saleor:3.23.0:a1:*:*:*:*:*:* Versions 3.23.0 a1 Vulnerable ·saleor
- cpe:2.3:a:saleor:saleor:3.23.0:a2:*:*:*:*:*:* Versions 3.23.0 a2 Vulnerable ·saleor
Remediation
- Fix · CNA saleor (saleor) Fixed in 3.20.118, 3.21.54, 3.22.47, 3.23.0a3
Timeline
- 2026-10-02 Threatist record created from CVE-2026-35407
References
Patch 5
- https://github.com/saleor/saleor/commit/7be352fa8c35875d6e66d36493ca7c14c101bd64
- https://github.com/saleor/saleor/commit/cdb66da97abb7c86939e384914cd8d9194f378e8
- https://github.com/saleor/saleor/commit/d6a94e95bd77f3f733fa66afd1b1ac72e863ca2a
- https://github.com/saleor/saleor/commit/e42aa4d6e588982e78942b033af051c8ec8f43fa
- https://github.com/saleor/saleor/commit/f0371bdd4cafcc841f1a9e7049cead6133bf7464
More Saleor vulnerabilities
- 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-18341 Saleor lacks proper HTML sanitization in rich text fields CVSS 4.0HIGH 7.2
- TI-2022-18651 Improper object type validation in saleor CVSS 3.1MEDIUM 5.3
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences