{"id":"CVE-2020-15245","url":"https://www.cyber-defence.io/tools/cve/CVE-2020-15245","generatedAt":"2026-10-27T20:22:32.033Z","title":"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.","description":"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.","published":"2020-10-19T21:15:13.000Z","lastModified":"2026-06-17T02:56:21.000Z","status":"Modified","sourceIdentifier":"security-advisories@github.com","cvss":{"version":"3.1","score":4.3,"severity":"MEDIUM","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N"},"cwe":["CWE-79","CWE-862"],"affected":["sylius/sylius"],"epss":{"score":0.00627,"percentile":0.49776,"date":"2026-10-26","history":[]},"kev":{"listed":false},"exploits":{"count":0,"verified":false,"firstPublished":null,"source":"Exploit-DB (https://gitlab.com/exploit-database/exploitdb)","entries":[]},"verdict":{"level":"low","text":"Lower severity and a low EPSS score (0.63%). Track it; it rarely justifies an emergency change on its own."},"changes":[],"references":[{"url":"https://github.com/Sylius/Sylius/commit/60636d711a4011e8694d10d201b53632c7e8ecaf","tags":["Patch","Third Party Advisory"],"source":"security-advisories@github.com"},{"url":"https://github.com/Sylius/Sylius/security/advisories/GHSA-6gw4-x63h-5499","tags":["Mitigation","Third Party Advisory"],"source":"security-advisories@github.com"},{"url":"https://github.com/Sylius/Sylius/commit/60636d711a4011e8694d10d201b53632c7e8ecaf","tags":["Patch","Third Party Advisory"],"source":"af854a3a-2127-422b-91ae-364da2661108"},{"url":"https://github.com/Sylius/Sylius/security/advisories/GHSA-6gw4-x63h-5499","tags":["Mitigation","Third Party Advisory"],"source":"af854a3a-2127-422b-91ae-364da2661108"}],"sources":{"nvd":"https://nvd.nist.gov/vuln/detail/CVE-2020-15245","epss":"https://www.first.org/epss/","kev":"https://www.cisa.gov/known-exploited-vulnerabilities-catalog","exploitdb":"https://www.exploit-db.com/"},"licence":"CC BY 4.0 — link back to the CVE Explorer if you publish the results; upstream data remains subject to its own terms."}