CVE-2020-15245

Email verification bypass in Sylius

MEDIUM
4.3
CVSS Score
Published: October 19, 2020 at 08:50 PM UTC
Updated: June 17, 2026 at 02:56 AM UTC
1 product affected across 1 vendorSylius

Using Sylius by Sylius?

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

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM4.3
Exploit prediction
EPSS 0.6%

Description

In Sylius before versions 1.6.9, 1.7.9 and 1.8.3, the user may register in a shop by email [email protected], verify it, change it to the mail [email protected] and stay verified and enabled. This may lead to having accounts addressed to totally different emails, that were verified. Note, that this way one is not able to take over any existing account (guest or normal one). The issue has been patched in Sylius 1.6.9, 1.7.9 and 1.8.3. As a workaround, you may resolve this issue on your own by creating a custom event listener, which will listen to the sylius.customer.pre_update event. You can determine that email has been changed if customer email and user username are different. They are synchronized later on. Pay attention, to email changing behavior for administrators. You may need to skip this logic for them. In order to achieve this, you should either check master request path info, if it does not contain /admin prefix or adjust event triggered during customer update in the shop. You can find more information on how to customize the event here.

Affected

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

95%
v < 1.6.9v < 9.4.41.7.0 ≤ v < 1.7.91.8.0 ≤ v < 1.8.3
Affected range stops below 1.6.9, so it looks safe — our inference, not a vendor statement
Affected range stops below 1.7.9, so it looks safe — our inference, not a vendor statement
Affected range stops below 1.8.3, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.4.4, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

CVSS

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

Quick Info

StatusMODIFIED
CWE
CWE-79CWE-862

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