Skip to content
Fencer Intel
medium 5.0

CVE-2022-24742 json

Exposure of Sensitive Information Due to Incompatible Policies in Sylius

published 4y ago modified 4mo ago also GHSA-7563-75j9-6h5p , EUVD-2022-1352

cvss
5.0
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.8%
EPSS 0.8% chance of exploitation in 30 days, percentile 57%
public exploits
0
none known

Summary

Sylius is an open source eCommerce platform. Prior to versions 1.9.10, 1.10.11, and 1.11.2, any other user can view the data if browser tab remains unclosed after log out. The issue is fixed in versions 1.9.10, 1.10.11, and 1.11.2. A workaround is available. The application must strictly redirect to login page even browser back button is pressed. Another possibility is to set more strict cache policies for restricted content.

Patch / fix

  • packagist sylius/sylius 1.9.10, 1.10.11, 1.11.2
  • sylius sylius 1.9.10, 1.10.11, 1.11.2

Is CVE-2022-24742 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
last yr.

Exploit prediction

0.82% chance of exploitation in the next 30 days, higher than 57% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 5.0 CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N
NVD 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:P/I:N/A:N
GitHub 3.1 5.0 CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
packagist sylius/sylius
<1.9.10
>=1.10, <1.10.11
>=1.11, <1.11.2
1.9.10
1.10.11
1.11.2

Affected products

  • Sylius Sylius

Classification

Weakness
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
  • CWE-668 Exposure of Resource to Wrong Sphere
  • CWE-213 Exposure of Sensitive Information Due to Incompatible Policies

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.