dbcve.org
SyliusApplication

CVE-2022-24733

MEDIUM · 6.1 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 →
68/100
Remediation priority · Elevated
Remotely reachable 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, it is possible for a page controlled by an attacker to load the website within an iframe. This will enable a clickjacking attack, in which the attacker's page overlays the target application's interface with a different interface provided by the attacker. The issue is fixed in versions 1.9.10, 1.10.11, and 1.11.2. A workaround is available. Every response from app should have an X-Frame-Options header set to: ``sameorigin``. To achieve that, add a new `subscriber` in the app.

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 lack the X-Frame-Options HTTP header on responses, allowing the application to be embedded within iframes on attacker-controlled pages and enabling clickjacking attacks where malicious overlays trick users into performing unintended actions.

MitigationConfigure the application to include the X-Frame-Options: sameorigin header on all HTTP responses, either by upgrading to a patched version or implementing a Symfony event subscriber that adds this header to every response.

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
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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
    Locate the composer.json file in your Sylius installation root and check the 'sylius/sylius' version entry, or run 'composer show sylius/sylius | grep version' if you have CLI access
    Affected if The version is below 1.9.10, between 1.10.0-1.10.11, or between 1.11.0-1.11.2
  2. Verify X-Frame-Options header presence
    Send a request to your Sylius storefront (e.g., curl -I https://your-storefront.com/) and inspect the response headers for 'X-Frame-Options'
    Affected if The X-Frame-Options header is missing from the HTTP response
  3. Confirm iframe embedding is possible
    Create a simple HTML page with an iframe pointing to your Sylius storefront and open it in a browser, or use curl to check the page loads inside a frame
    Affected if The Sylius storefront loads successfully inside an iframe on a different domain, confirming the missing header is exploitable
  4. Check for alternative frame protection
    Inspect HTTP response headers for Content-Security-Policy header containing 'frame-ancestors' directive, which can also mitigate clickjacking
    Affected if No X-Frame-Options header is present AND no CSP frame-ancestors directive exists to block iframe embedding

You are affected if your Sylius version falls within the vulnerable ranges AND HTTP responses lack X-Frame-Options header (or equivalent CSP frame-ancestors protection), allowing your site to be embedded in iframes on attacker-controlled pages.

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 the application to include the X-Frame-Options: sameorigin header on all HTTP responses, either by upgrading to a patched version or implementing a Symfony event subscriber that adds this header to every response.

Recommended fix High confidence

1.9.10, 1.10.11, or 1.11.2 depending on your current version branch

  1. Determine your current Sylius version by checking your composer.json or installation
  2. Identify which version branch you are on (1.9.x, 1.10.x, or 1.11.x)
  3. Upgrade to the appropriate fixed version: 1.9.10 for 1.9.x users, 1.10.11 for 1.10.x users, or 1.11.2 for 1.11.x users
  4. Run 'composer update sylius/sylius --no-interaction' to apply the upgrade
  5. Verify the upgrade was successful by checking theSylius version
  6. Test that the X-Frame-Options: sameorigin header is now present in responses (or implement the subscriber workaround if upgrade is delayed)
Caveat Standard Sylius minor upgrades typically maintain backward compatibility but review release notes for any breaking changes specific to your version path

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

Fix this in Sylius Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-24733 — 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-24733 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