cve.bz

CVE-2022-24743 sylius sylius: Insufficient Session Expiration

8.2 highExploit referenceEPSS 1.3%Fix available

High (8.2) in sylius sylius. EPSS 1.3% estimated probability of exploitation activity in the next 30 days. Fixed in sylius/sylius 1.10.11, 1.11.2.

On this page
Sylius is an open source eCommerce platform. Prior to versions 1.10.11 and 1.11.2, the reset password token was not set to null after the password was changed. The same token could be used several times, which could result in leak of the existing token and unauthorized password change. The issue is fixed in versions 1.10.11 and 1.11.2. As a workaround, overwrite the `Sylius\Bundle\ApiBundle\CommandHandler\ResetPasswordHandler` class with code provided by the maintainers and register it in a container. More information about this workaround is available in the GitHub Security Advisory.

Severity

CVSS 3.1

8.2 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N
EPSS
1.3% (unchanged from 1.3% a week ago; 1.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 70th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: partial, assessed 2025-04-22. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-613 Insufficient Session Expiration deprecated by MITRE see CWE-1463, CWE-1464
OWASP Top 10
A07:2025 Authentication Failures
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

  • sylius/sylius (Packagist): fixed in 1.10.11, 1.11.2

Ask an AI about this CVE

Show the promptExplain CVE-2022-24743 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2022-24743?via=ask-ai-copy and https://cve.bz/cve/CVE-2022-24743?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2022-24743 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
sylius:syliusfrom 1.10.0 before 1.10.11
sylius:syliusfrom 1.11.0 before 1.11.2

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-mf3v-f2qq-pf9gPackagistsylius/sylius>=1.10.0 <1.10.111.10.11
GHSA-mf3v-f2qq-pf9gPackagistsylius/sylius>=1.11.0 <1.11.21.11.2

References

Check your stackJSON