CVE-2020-15245 json
Email verification bypass in Sylius
published 2020-10-19 6 y ago modified 2026-09-10 1 mo ago also GHSA-6gw4-x63h-5499 , EUVD-2020-1416
- cvss
- 4.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 50%
- public exploits
- 0
- none known
Summary
In Sylius before versions 1.6.9, 1.7.9 and 1.8.3, the user may register in a shop by email mail@example.com, verify it, change it to the mail another@domain.com 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.
Patch / fix
- packagist sylius/sylius 1.6.9, 1.7.9, 1.8.3
- sylius sylius 1.6.9, 1.7.9, 1.8.3
Exploit prediction
0.63% chance of exploitation in the next 30 days, higher than 50% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N |
| NVD | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N |
| NVD | 2.0 | 4.0 | AV:N/AC:L/Au:S/C:N/I:P/A:N |
| GitHub | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | sylius/sylius | >=1.7.0, <1.7.9 >=1.8.0, <1.8.3 >=1.0.0, <1.6.9 |
1.7.9 1.8.3 1.6.9 |
Affected products
- Sylius Sylius
Classification
References
-
github.com
/Sylius/Sylius/commit/60636d711a4011e8694d10d201b53632c7e8ecaf
web, patch, third-party-advisory
-
github.com
/Sylius/Sylius/security/advisories/GHSA-6gw4-x63h-5499
web, mitigation, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2020-15245
advisory
-
github.com
/FriendsOfPHP/security-advisories/blob/master/sylius/sylius/CVE-2020-15245.yaml
web
-
github.com
/Sylius/Sylius
package
Sources
- CVE List CVE-2020-15245
- GitHub Advisory GHSA-6gw4-x63h-5499
- NVD CVE-2020-15245
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.