CVE-2020-15245

What it is

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.

At a glance

Exploitability

Can be exploited over the network with a low-privilege account. Limited direct impact.

Exploit odds

0.6% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2020-10-19 21:15 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 02:56 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.6% in the next 30 days (EPSS).
• Severity: 4.3 MEDIUM (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2020-10-19 21:15 UTC

Last modified

2026-06-17 02:56 UTC

Exploit probability

0.6% · EPSS, next 30 days

Weakness

CWE-79 · Cross-site scripting

Record status

Modified

Affected

• Sylius < 1.6.9
• Sylius < 1.7.9
• Sylius < 1.8.3

Attack profile CVSS 3.1 · 4.3

Attack vector

Network

Complexity

Low

Privileges needed

Low

User interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

Low

Availability

None

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2020-15245.md and follow it. Check whether this project is affected by CVE-2020-15245. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge