Approved changes feed: RSS · Atom
cpe:2.3:a:saleor:saleor:3.23.0:a1:*:*:*:*:*:*
part: a version: 3.23.0 update: a1
| Vendor | Saleor (fbec566e-ae4f-5c49-a898-f36a646d9d76) |
|---|---|
| Product | Saleor (e31d7f02-6ba6-5f8b-83dc-f92e4c4d9836) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from purl2cpe mapping |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/saleor/saleor |
purl2cpe | 2026-06-01 10:13:18.664489 |
pkg:pypi/saleor |
purl2cpe | 2026-06-01 10:13:18.664491 |
pkg:sourceforge/saleor.mirror |
purl2cpe | 2026-06-01 10:13:18.664493 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-35407 |
vulnerable | 2026-06-08 07:59:13.851768 |
Saleor has Cross-Account Email Change via Unbound Confirmation Token
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.
Published: 2026-04-08T17:24:39.716Z
Updated: 2026-04-10T20:36:19.733Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.