Skip to main content
No exploitation reportedFix available

CVE-2020-15245

No exploitation reported by the sources we read.

  • Published2020-10-19
  • Fixed in1.8.3 · 1.7.9 · 1.6.9
  • WeaknessCWE-79 · CWE-862

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

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.

Timeline

dates in UTC
  1. 2020-10-1921:15CVE publishedNVD

Versions per branch

NVD · OSV
Sylius
BranchAffectedFixed in
1.8≥ 1.8.0, < 1.8.31.8.3
1.7≥ 1.7.0, < 1.7.91.7.9
1.6< 1.6.91.6.9
1.x≥ 1.0.0, < 1.6.91.6.9

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Fix

  1. Update Sylius to 1.8.3 · 1.7.9 · 1.6.9

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

  • CNACVSS 3.14.3known since 2026-10-23
  • NVDCVSS 3.14.3read 2026-10-23
  • NVDCVSS 2.04read 2026-10-23
  • CNAweakness (CWE)CWE-79known since 2026-10-23
  • NVDweakness (CWE)CWE-862read 2026-10-23
  • FIRST EPSSEPSS score0.6 %2026-11-18
  • OSVaffected packages—
  • GitHub AdvisoriesadvisoryMODERATE2020-10-19

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
Published
2020-10-19
Last Modified
2026-06-17
NVD status
Modified
GitHub Advisory
GHSA-6gw4-x63h-5499

Frequently asked questions

What is CVE-2020-15245?

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.

Is CVE-2020-15245 actively exploited?

Active exploitation of CVE-2020-15245 has not been confirmed. Its EPSS score was 0.6% on 2026-11-18, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2020-15245?

CVE-2020-15245 has a CVSS v3 base score of 4.3 (MEDIUM severity), with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N.

Running sylius/sylius? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month

Sources for this record