{"answers":{"affected":"6 open source packages ship an affected version, including sylius/sylius. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-15245 in the wild and no public exploit code.","fix":"Upgrade sylius/sylius to a fixed version for your release line: 1.6.9, 1.7.9 or 1.8.3.","what":"CVE-2020-15245 is a medium-severity vulnerability in Sylius, published on 19 Oct 2020. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-15245 and fix it if it is affected.\n\nWhat it is: CVE-2020-15245 is a medium-severity vulnerability in Sylius, published on 19 Oct 2020. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2020-15245 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- sylius/sylius (Packagist): affected from 1.0.0; fixed in 1.6.9\n- sylius/sylius (Packagist): affected from 1.0.0; fixed in 1.6.9\n- sylius/sylius (Packagist): affected from 1.7.0; fixed in 1.7.9\n- sylius/sylius (Packagist): affected from 1.7.0; fixed in 1.7.9\n- sylius/sylius (Packagist): affected from 1.8.0; fixed in 1.8.3\n- sylius/sylius (Packagist): affected from 1.8.0; fixed in 1.8.3\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2020-15245/ (Markdown: https://insights.sbomify.com/CVE-2020-15245/index.md)","id":"CVE-2020-15245","markdown":"https://insights.sbomify.com/CVE-2020-15245/index.md","name":"CVE-2020-15245","record":{"aliases":["GHSA-6gw4-x63h-5499"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Sylius e-commerce platform","requires_auth":"low_privilege","summary":"Attackers can bypass email verification by changing their email after initial verification, resulting in unverified accounts being marked as verified.","user_interaction":"not_required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"sylius","vendor":"sylius"}],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"},{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"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.","ecosystems":["Packagist"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Email verification bypass in Sylius","id":"CVE-2020-15245","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"business_logic","year":"2020"},"n_packages":6,"n_references":2,"next":{"headline":"Local File Inclusion by unauthenticated users","id":"CVE-2020-15246"},"packages":[{"ecosystem":"Packagist","fixed":["1.6.9"],"introduced":["1.0.0"],"last_affected":[],"package":"sylius/sylius","purl":null,"source":"GHSA-6gw4-x63h-5499"},{"ecosystem":"Packagist","fixed":["1.6.9"],"introduced":["1.0.0"],"last_affected":[],"package":"sylius/sylius","purl":"pkg:composer/sylius/sylius","source":"GHSA-6gw4-x63h-5499"},{"ecosystem":"Packagist","fixed":["1.7.9"],"introduced":["1.7.0"],"last_affected":[],"package":"sylius/sylius","purl":null,"source":"GHSA-6gw4-x63h-5499"},{"ecosystem":"Packagist","fixed":["1.7.9"],"introduced":["1.7.0"],"last_affected":[],"package":"sylius/sylius","purl":"pkg:composer/sylius/sylius","source":"GHSA-6gw4-x63h-5499"},{"ecosystem":"Packagist","fixed":["1.8.3"],"introduced":["1.8.0"],"last_affected":[],"package":"sylius/sylius","purl":null,"source":"GHSA-6gw4-x63h-5499"},{"ecosystem":"Packagist","fixed":["1.8.3"],"introduced":["1.8.0"],"last_affected":[],"package":"sylius/sylius","purl":"pkg:composer/sylius/sylius","source":"GHSA-6gw4-x63h-5499"}],"prev":{"headline":"RCE in Magento","id":"CVE-2020-15244"},"products":["Sylius"],"published":"2020-10-19","related":[{"cvss_score":8.2,"headline":"Sylius has a Promotion Usage Limit Bypass via Race Condition","id":"CVE-2026-31824","kev_date_added":null,"published":"2026-03-10"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2024-57610","kev_date_added":null,"published":"2025-02-06"},{"cvss_score":7.1,"headline":"Sylius affected by IDOR in Cart and Checkout LiveComponents","id":"CVE-2026-31820","kev_date_added":null,"published":"2026-03-10"},{"cvss_score":7.1,"headline":"Insufficient Session Expiration in Sylius","id":"CVE-2022-24743","kev_date_added":null,"published":"2022-03-14"},{"cvss_score":6.9,"headline":"Sylius has an Open Redirect via Referer Header","id":"CVE-2026-31819","kev_date_added":null,"published":"2026-03-10"},{"cvss_score":6.9,"headline":"Sylius is Missing Authorization in API v2 Add Item Endpoint","id":"CVE-2026-31821","kev_date_added":null,"published":"2026-03-10"},{"cvss_score":6.4,"headline":"Sylius has potential Cross Site Scripting vulnerability via the \"Province\" field in the Checkout and Address Book","id":"CVE-2024-29376","kev_date_added":null,"published":"2024-04-22"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["Sylius"]},"summary":"Attackers can bypass email verification by changing their email after initial verification, resulting in unverified accounts being marked as verified.","url":"https://insights.sbomify.com/CVE-2020-15245/"}