CVE-2026-39851

Saleor has a user enumeration vulnerability due to different error messages

MEDIUM
4.3
CVSS Score
Published: April 8, 2026 at 05:33 PM UTC
Updated: July 24, 2026 at 09:20 PM UTC
1 product affected across 1 vendorSaleor

Using saleor by saleor?

Get instant alerts when new vulnerabilities affect saleor - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM4.3
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

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, the requestEmailChange() mutation was revealing the existence of user-provided email addresses in error messages. This vulnerability is fixed in 3.23.0a3, 3.22.47, 3.21.54, and 3.20.118.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 3.20.118v < 3.21.54v < 3.22.47v < 3.23.0a32.10.0 ≤ v < 3.20.1183.21.0 ≤ v < 3.21.543.22.0 ≤ v < 3.22.473.23.0 alpha03.23.0 alpha13.23.0 alpha2
Affected range stops below 3.20.118, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.21.54, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.22.47, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.23.0a3, so it looks safe — our inference, not a vendor statement

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
NETWORK
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
LOW
Integrity
NONE
Availability
NONE
Vector?

Quick Info

StatusANALYZED
CWE
CWE-204

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card