CVE-2026-31819
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 · uneditedSylius is an Open Source eCommerce Framework on Symfony. CurrencySwitchController::switchAction(), ImpersonateUserController::impersonateAction() and StorageBasedLocaleSwitcher::handle() use the HTTP Referer header directly when redirecting. The attack requires the victim to click a legitimate application link placed on an attacker-controlled page. The browser automatically sends the attacker's site as the Referer, and the application redirects back to it. This can be used for phishing or credential theft, as the redirect originates from a trusted domain. The severity varies by endpoint; public endpoints require no authentication and are trivially exploitable, while admin-only endpoints require an authenticated session but remain vulnerable if an admin follows a link from an external source such as email or chat. The issue is fixed in versions: 1.9.12, 1.10.16, 1.11.17, 1.12.23, 1.13.15, 1.14.18, 2.0.16, 2.1.12, 2.2.3 and above.
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 confidenceSylius eCommerce framework contains an open redirect vulnerability in CurrencySwitchController, ImpersonateUserController, and StorageBasedLocaleSwitcher. These components use the HTTP Referer header directly for redirects without validation, allowing attackers to craft malicious links that redirect victims from a trusted domain to attacker-controlled sites for phishing or credential theft.
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< 1.9.12>= 1.10.0, < 1.10.16>= 1.11.0, < 1.11.17>= 1.12.0, < 1.12.23>= 1.13.0, < 1.13.15>= 1.14.0, < 1.14.18>= 2.0.0, < 2.0.16>= 2.1.0, < 2.1.12>= 2.2.0, < 2.2.3CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Determine installed Sylius versionCheck the composer.lock file or composer.json in your project root for the 'sylius/sylius' package version, or look for a VERSION file in the project rootAffected if The installed version falls into any of these ranges: < 1.9.12, >= 1.10.0 and < 1.10.16, >= 1.11.0 and < 1.11.17, >= 1.12.0 and < 1.12.23, >= 1.13.0 and < 1.13.15, >= 1.14.0 and < 1.14.18, >= 2.0.0 and < 2.0.16, >= 2.1.0 and < 2.1.12, or >= 2.2.0 and < 2.2.3
-
Identify affected controllers in codebaseSearch for the classes CurrencySwitchController, ImpersonateUserController, and StorageBasedLocaleSwitcher in your vendor or src directory - typically under src/Controller/ or vendor/sylius/sylius/src/Sylius/Bundle/ShopBundle/Controller/Affected if These controller classes exist in your installation and are being used by the application
-
Check redirect logic for Referer header usageExamine the source code of the three identified controllers, specifically looking for any redirect() or $this->redirect() calls that incorporate the HTTP Referer header without validationAffected if The controllers contain redirect logic that uses the Referer header (such as $request->headers->get('Referer') or $_SERVER['HTTP_REFERER']) without sanitizing or validating the value before performing the redirect
You are affected if your installed Sylius version is within any of the vulnerable ranges listed and your application uses any of the three controllers (CurrencySwitchController, ImpersonateUserController, or StorageBasedLocaleSwitcher) with redirect logic that trusts the Referer header.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.9.121.10.161.11.17
Implement strict allowlist validation for redirect destinations, ignoring or validating the Referer header before performing any redirect. For admin endpoints, add additional CSRF protections and consider requiring re-authentication for sensitive redirect operations.
Upgrade to 1.12.23 (if on 1.12 branch), 1.14.18 (if on 1.13/1.14 branch), 2.2.3 (if on 2.x branch), or the appropriate fixed version for your branch (1.9.12, 1.10.16, 1.11.17, 1.13.15, 2.0.16, 2.1.12)
- 1. Identify your current Sylius version by checking your composer.json or installed version
- 2. Determine which version branch you are on (e.g., 1.9.x, 1.10.x, 1.11.x, 1.12.x)
- 3. Run 'composer require sylius/sylius:VERSION' replacing VERSION with your target fixed version
- 4. Clear the application cache after upgrading: 'php bin/console cache:clear'
- 5. Run database migrations if any: 'php bin/console doctrine:migrations:migrate'
- 6. Test the affected endpoints (currency switch, user impersonate, locale switch) to confirm redirects no longer use untrusted Referer headers
- 7. Verify your application functions normally after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-31819 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-31819 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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