Sensitive Information Exposure in Sylius

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.0 · CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N

EPSS

• CVE-2022-24742: 0.82% estimated exploitation activity in the next 30 days; percentile 57.35 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact Any other user can view the data if the browser tab remains open after logging out. Once someone logs out and leaves the browser open, the potential attacker may use the back button to see the content exposed on given screens. No action may be performed though, and any website refresh will block further reads. It may, however, lead to a data leak, like for example customer details, payment gateway configuration, etc.- but only if these were pages checked by the administrator. This vulnerability requires full access to the computer to take advantage of it. Patches The issue is fixed in versions: 1.9.10, 1.10.11, 1.11.2 and above. Workarounds The application must strictly redirect to the login page even when the browser back button is pressed. Another possibility is to set more strict cache policies for restricted content (like no-store). It can be achieved with the following class: After that register service in the container: The code above requires changes in…

Published by the source

14 Mar 2022, 22:26 UTC

Last modified by the source

30 Jun 2023, 21:35 UTC

Source last checked

26 Oct 2026, 14:06 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-7563-75j9-6h5p

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

# Patch Next advisory brief: CVE-2022-24742

Advisory: Sensitive Information Exposure in Sylius
IDs: CVE-2022-24742, GHSA-7563-75j9-6h5p
Record: https://patchnext.com/advisories/cve-2022-24742 (revision 1, source checked 26 Oct 2026, 14:06 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.0)
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.11.2, 1.10.11, 1.9.10. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist sylius/sylius: affected < 1.9.10; >= 1.10, < 1.10.11; >= 1.11, < 1.11.2; fixed in 1.10.11, 1.11.2, 1.9.10

## 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-7563-75j9-6h5p (GitHub-reviewed advisory GHSA-7563-75j9-6h5p lists affected ranges: Packagist sylius/sylius >=0 =1.10 =1.11 <1.11.2)

Commands are suggestions: review each one before running it.