dbcve.org
SyliusApplication

CVE-2022-24742

MEDIUM · 5.5 CVSS v3.1 Published 2022-03-14
Fix available
A fix is available. Upgrade to 1.9.10 / 1.10.11 or later.
See remediation →
58/100
Remediation priority · Elevated
No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Sylius eCommerce platform versions prior to 1.9.10, 1.10.11, and 1.11.2 fail to properly clear sensitive user data from browser cache after logout. When a user logs out while keeping a browser tab open, cached page content remains accessible to other users who open the same browser, allowing unauthorized viewing of previous session data.

MitigationConfigure strict cache-control headers (no-store, no-cache, must-revalidate, private) for all authenticated pages and implement server-side redirects to the login page when the back button is pressed after logout.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
SyliusApplication
Affected:< 1.9.10>= 1.10.0, < 1.10.11>= 1.11.0, < 1.11.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Sylius version
    Check the composer.json file in the project root for the 'sylius/sylius' package version, or run 'composer show sylius/sylius' to see the installed version
    Affected if The version is below 1.9.10, between 1.10.0 and 1.10.11, or between 1.11.0 and 1.11.2
  2. Inspect cache-control headers on authenticated routes
    Log into the admin panel, then log out while keeping a browser tab open. Use browser developer tools (Network tab) to inspect HTTP response headers on authenticated pages, specifically looking for Cache-Control headers
    Affected if Authenticated pages do not include 'no-store' or 'no-cache' directives in their Cache-Control header, allowing cached content to persist after logout
  3. Review security configuration for cache headers
    Examine the Sylius security configuration files (typically in config/packages/security.yaml or similar) and check if the firewall configuration for admin/Shop areas includes proper cache header settings
    Affected if The security configuration lacks cache-control directives (no-store, no-cache, must-revalidate, private) for authenticated areas
  4. Test browser cache persistence after logout
    Log into the admin panel, navigate to a page with sensitive data, then log out. Attempt to access the previous page URL directly or use the browser back button to see if cached content remains visible
    Affected if Cached page content from the previous session remains accessible after logout

A user is affected if their Sylius installation version falls within the vulnerable ranges AND proper cache-control headers are not configured for authenticated pages, allowing cached sensitive data to persist after logout.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.9.10 / 1.10.11 / 1.11.2 or later
Fixed in 1.9.101.10.111.11.2
Interim mitigation

Configure strict cache-control headers (no-store, no-cache, must-revalidate, private) for all authenticated pages and implement server-side redirects to the login page when the back button is pressed after logout.

Recommended fix High confidence

Upgrade to Sylius 1.9.10 (for 1.9.x), 1.10.11 (for 1.10.x), or 1.11.2 (for 1.11.x)

  1. Identify your current Sylius version branch (1.9.x, 1.10.x, or 1.11.x) by checking your composer.json or installed version
  2. For 1.9.x branch: upgrade to version 1.9.10 or later
  3. For 1.10.x branch: upgrade to version 1.10.11 or later
  4. For 1.11.x branch: upgrade to version 1.11.2 or later
  5. Run composer update sylius/sylius to apply the changes
  6. Clear the application cache after upgrade (bin/console cache:clear)
  7. Test logout behavior: log in, access restricted content, log out, then press the browser back button to verify sensitive data is not displayed from cache
  8. As an alternative configuration workaround, ensure your web server and application set Cache-Control: no-store, no-cache, must-revalidate headers for all authenticated routes
Caveat Point releases typically have minimal breaking changes; review the release notes for your version branch for any deprecation notices

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Sylius Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-24742 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-24742 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data