Metrics
Affected Vendors & Products
No advisories yet.
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
Fri, 10 Apr 2026 21:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
cvssV3_1
|
Wed, 08 Apr 2026 20:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Saleor
Saleor saleor |
|
| Vendors & Products |
Saleor
Saleor saleor |
Wed, 08 Apr 2026 18:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | Saleor has Cross-Account Email Change via Unbound Confirmation Token | |
| Weaknesses | CWE-285 | |
| References |
|
|
| Metrics |
cvssV4_0
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-04-10T20:36:19.733Z
Reserved: 2026-04-02T17:03:42.075Z
Link: CVE-2026-35407
Updated: 2026-04-10T20:36:14.051Z
Status : Undergoing Analysis
Published: 2026-04-08T19:25:24.040
Modified: 2026-04-10T21:16:25.723
Link: CVE-2026-35407
No data.
OpenCVE Enrichment
Updated: 2026-04-09T08:28:04Z