Summary
Workarounds
If for whatever reason you are not able to upgrade your application version, 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.
Acknowledgements
This security issue has been reported by Mircea Silviu (@decemvre), thanks a lot!
For more information
If you have any questions or comments about this advisory:
- Email us at [email protected]
Impact
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).
Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.
CVE-2020-15245 has a CVSS score of 4.3 (Medium). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.7.9, 1.8.3, 1.6.9); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
Patch has been provided for Sylius 1.6.x and newer - 1.6.9, 1.7.9, 1.8.3. Versions older than 1.6 are not covered by our security support anymore.
Frequently Asked Questions
- What is CVE-2020-15245? CVE-2020-15245 is a medium-severity cross-site scripting (XSS) vulnerability in sylius/sylius (composer), affecting versions >= 1.7.0, < 1.7.9. It is fixed in 1.7.9, 1.8.3, 1.6.9. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
- How severe is CVE-2020-15245? CVE-2020-15245 has a CVSS score of 4.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of sylius/sylius are affected by CVE-2020-15245? sylius/sylius (composer) versions >= 1.7.0, < 1.7.9 is affected.
- Is there a fix for CVE-2020-15245? Yes. CVE-2020-15245 is fixed in 1.7.9, 1.8.3, 1.6.9. Upgrade to this version or later.
- Is CVE-2020-15245 exploitable, and should I be worried? Whether CVE-2020-15245 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2020-15245 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2020-15245?
- Upgrade
sylius/syliusto 1.7.9 or later - Upgrade
sylius/syliusto 1.8.3 or later - Upgrade
sylius/syliusto 1.6.9 or later
- Upgrade