CVE-2026-31822
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. A cross-site scripting (XSS) vulnerability exists in the shop checkout login form handled by the ApiLoginController Stimulus controller. When a login attempt fails, AuthenticationFailureHandler returns a JSON response whose message field is rendered into the DOM using innerHTML, allowing any HTML or JavaScript in that value to be parsed and executed by the browser. The issue is fixed in versions: 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 confidenceA reflected XSS vulnerability exists in Sylius' shop checkout login form. The AuthenticationFailureHandler returns a JSON response containing an error message when login fails, and this message is rendered directly into the DOM using innerHTML without sanitization, allowing arbitrary JavaScript execution.
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>= 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.
-
Check installed Sylius versionLocate the composer.json file or use composer show sylius/sylius to retrieve the installed version numberAffected if The version is >= 2.0.0 and < 2.0.16, OR >= 2.1.0 and < 2.1.12, OR >= 2.2.0 and < 2.2.3
-
Verify shop checkout login form is enabledConfirm that the Sylius shop channel is configured and the checkout login step is accessible in the applicationAffected if The shop checkout login functionality is active and reachable
-
Identify AuthenticationFailureHandler configurationLocate the security configuration file (typically security.yaml or security.yaml.dist) and find the entry for AuthenticationFailureHandlerAffected if The handler is configured to return JSON responses on authentication failures
-
Inspect frontend error rendering codeFind the Stimulus controller responsible for handling login form errors and check if it uses innerHTML to render error messages from the JSON responseAffected if The controller uses innerHTML (rather than textContent) to insert error messages into the DOM
The environment is affected if Sylius version falls within any of the affected ranges AND the shop checkout login form with JSON error handling is in use.
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 · scoped2.0.162.1.122.2.3
Upgrade to fixed versions 2.0.16, 2.1.12, or 2.2.3+. Alternatively, modify the frontend Stimulus controller to use textContent instead of innerHTML when rendering error messages.
Sylius 2.0.16, 2.1.12, or 2.2.3 (depending on your current major.minor version)
- Identify the current Sylius version by checking your composer.json or installed version
- For Sylius 2.0.x versions: upgrade to version 2.0.16 by running 'composer require sylius/sylius:^2.0.16' or 'composer update sylius/sylius:2.0.16'
- For Sylius 2.1.x versions: upgrade to version 2.1.12 by running 'composer require sylius/sylius:^2.1.12' or 'composer update sylius/sylius:2.1.12'
- For Sylius 2.2.x versions: upgrade to version 2.2.3 by running 'composer require sylius/sylius:^2.2.3' or 'composer update sylius/sylius:2.2.3'
- Clear the application cache after upgrade with 'php bin/console cache:clear'
- Verify the upgrade was successful and test the checkout login flow
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.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 $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-31822 — 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-31822 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