Saleor up to 3.20.117/3.21.53/3.22.46/3.23.0a2 Email Change Confirmation Token new_email improper authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.0 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, has been found in Saleor up to 3.20.117/3.21.53/3.22.46/3.23.0a2. This impacts an unknown function of the component Email Change Confirmation Token. Performing a manipulation of the argument new_email results in improper authorization. This vulnerability was named CVE-2026-35407. The attack may be initiated remotely. There is no available exploit. It is advisable to upgrade the affected component.
Details
A vulnerability was found in Saleor up to 3.20.117/3.21.53/3.22.46/3.23.0a2. It has been classified as critical. This affects an unknown functionality of the component Email Change Confirmation Token. The manipulation of the argument new_email with an unknown input leads to a improper authorization vulnerability. CWE is classifying the issue as CWE-285. The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action. This is going to have an impact on integrity, and availability. The summary by CVE is:
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.
It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2026-35407 since 04/02/2026. The exploitability is told to be difficult. It is possible to initiate the attack remotely. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1548.002 according to MITRE ATT&CK.
Upgrading to version 3.20.118, 3.21.54, 3.22.47 or 3.23.0a3 eliminates this vulnerability.
Be aware that VulDB is the high quality source for vulnerability data.
Product
Name
Version
- 3.20.117
- 3.21.0
- 3.21.1
- 3.21.2
- 3.21.3
- 3.21.4
- 3.21.5
- 3.21.6
- 3.21.7
- 3.21.8
- 3.21.9
- 3.21.10
- 3.21.11
- 3.21.12
- 3.21.13
- 3.21.14
- 3.21.15
- 3.21.16
- 3.21.17
- 3.21.18
- 3.21.19
- 3.21.20
- 3.21.21
- 3.21.22
- 3.21.23
- 3.21.24
- 3.21.25
- 3.21.26
- 3.21.27
- 3.21.28
- 3.21.29
- 3.21.30
- 3.21.31
- 3.21.32
- 3.21.33
- 3.21.34
- 3.21.35
- 3.21.36
- 3.21.37
- 3.21.38
- 3.21.39
- 3.21.40
- 3.21.41
- 3.21.42
- 3.21.43
- 3.21.44
- 3.21.45
- 3.21.46
- 3.21.47
- 3.21.48
- 3.21.49
- 3.21.50
- 3.21.51
- 3.21.52
- 3.21.53
- 3.22.0
- 3.22.1
- 3.22.2
- 3.22.3
- 3.22.4
- 3.22.5
- 3.22.6
- 3.22.7
- 3.22.8
- 3.22.9
- 3.22.10
- 3.22.11
- 3.22.12
- 3.22.13
- 3.22.14
- 3.22.15
- 3.22.16
- 3.22.17
- 3.22.18
- 3.22.19
- 3.22.20
- 3.22.21
- 3.22.22
- 3.22.23
- 3.22.24
- 3.22.25
- 3.22.26
- 3.22.27
- 3.22.28
- 3.22.29
- 3.22.30
- 3.22.31
- 3.22.32
- 3.22.33
- 3.22.34
- 3.22.35
- 3.22.36
- 3.22.37
- 3.22.38
- 3.22.39
- 3.22.40
- 3.22.41
- 3.22.42
- 3.22.43
- 3.22.44
- 3.22.45
- 3.22.46
- 3.23.0a2
Website
- Product: https://github.com/saleor/saleor/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 4.2VulDB Meta Temp Score: 4.0
VulDB Base Score: 4.2
VulDB Temp Score: 4.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Improper authorizationCWE: CWE-285 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Saleor 3.20.118/3.21.54/3.22.47/3.23.0a3
Timeline
04/02/2026 CVE reserved04/08/2026 Advisory disclosed
04/08/2026 VulDB entry created
04/08/2026 VulDB entry last update
Sources
Product: github.comAdvisory: github.com
Status: Confirmed
CVE: CVE-2026-35407 (🔒)
GCVE (CVE): GCVE-0-2026-35407
GCVE (VulDB): GCVE-100-356343
Entry
Created: 04/08/2026 20:55Changes: 04/08/2026 20:55 (67)
Complete: 🔍
Cache ID: 216::103
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.