Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 4.3

Ability to switch customer email address on account detail page and stay verified

CVE-2020-15245GHSA-6gw4-x63h-5499

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (sylius/sylius 1.8.3, 1.7.9, 1.6.9), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Packagist sylius/sylius

    Affected
    >= 1.7.0, < 1.7.9>= 1.8.0, < 1.8.3>= 1.0.0, < 1.6.9
    Fixed in
    1.6.9, 1.7.9, 1.8.3

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
4.3 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
EPSS
  • CVE-2020-15245: 0.63% estimated exploitation activity in the next 30 days; percentile 50.12 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Impact 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). Patches 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. 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.preupdate 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…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-6gw4-x63h-5499

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2020-15245

Advisory: Ability to switch customer email address on account detail page and stay verified
IDs: CVE-2020-15245, GHSA-6gw4-x63h-5499
Record: https://patchnext.com/advisories/cve-2020-15245 (revision 1, source checked 26 Oct 2026, 14:15 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: sylius/sylius 1.8.3, 1.7.9, 1.6.9. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist sylius/sylius: affected >= 1.7.0, < 1.7.9; >= 1.8.0, < 1.8.3; >= 1.0.0, < 1.6.9; fixed in 1.6.9, 1.7.9, 1.8.3

## Suggested inspection (read-only)
- Packagist sylius/sylius: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on sylius/sylius.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-6gw4-x63h-5499 (GitHub-reviewed advisory GHSA-6gw4-x63h-5499 lists affected ranges: Packagist sylius/sylius >=1.7.0 =1.8.0 =1.0.0 <1.6.9)

Commands are suggestions: review each one before running it.

Loading voting…