GHSA-VGH8-C6FP-7GCG
Vulnerability from github – Published: 2026-03-11 00:13 – Updated: 2026-03-11 20:32Impact
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 message value originates from AuthenticationException::getMessageKey() passed through Symfony's translator (security domain, using the request locale). In the default Sylius installation, this returns a hardcoded translation key (e.g. "Invalid credentials."), which is not directly user-controlled. However, using innerHTML with server-derived data violates defense-in-depth principles, and the risk escalates significantly under realistic scenarios:
- Customized authentication handlers — if a project overrides AuthenticationFailureHandler to include user-supplied data in the message (e.g. "No account found for "), an attacker can inject arbitrary JavaScript directly via the login
form without any privileged access.
- Translation injection — if translation files are sourced from an untrusted database or CMS and contain HTML, the message could carry a malicious payload.
- Man-in-the-Middle — if the response is intercepted (e.g. on HTTP or via a compromised proxy), an attacker can inject arbitrary HTML/JS into the message field.
- Server-side injection — if any middleware, reverse proxy, or error handler modifies the JSON response body, malicious content could be injected into the message field.
Exploitation could lead to session hijacking, credential theft, cart/order manipulation, or phishing within the trusted shop domain.
The vulnerability affects all Sylius installations that use the default shop checkout login form with the bundled ApiLoginController.js.
Patches
The issue is fixed in versions: 2.0.16, 2.1.12, 2.2.3 and above.
Workarounds
Override the vulnerable JavaScript controller at the project level.
Note: Step 2 differs between Sylius 2.0 and up
Step 1. Override JavaScript controller handling login
Patch ApiLoginController.js
Copy the original from vendor/sylius/sylius/src/Sylius/Bundle/ShopBundle/Resources/assets/controllers/ApiLoginController.js to assets/shop/controllers/ApiLoginController.js and apply:
...
.then(response => {
if (response.success) {
window.location.reload();
} else {
const errorElement = this.errorPrototypeTarget.cloneNode(true);
- errorElement.innerHtml = response.message;
+ errorElement.textContent = response.message;
this.errorTarget.innerHTML = errorElement.outerHTML;
}
})
...
Step 2. Register the patched controller
Sylius 2.1+ (Stimulus Bridge with
controllers.json)
Disable the vendor controller in assets/shop/controllers.json:
...
"api-login": {
- "enabled": true,
+ "enabled": false,
"fetch": "lazy"
}
...
Register the overwritten controller in assets/shop/bootstrap.js
import ApiLoginController from './controllers/ApiLoginController'
app.register('sylius--shop-bundle--api-login', ApiLoginController);
Sylius 2.0 (explicit imports in vendor
app.js)
Use Webpack's NormalModuleReplacementPlugin to swap the controller at build time. In webpack.config.js, after shopConfig is created:
+ const webpack = require('webpack');
...
// Shop config
const shopConfig = SyliusShop.getWebpackConfig(path.resolve(__dirname));
+ shopConfig.plugins.push(
+ new webpack.NormalModuleReplacementPlugin(
+ /\/controllers\/ApiLoginController\.js$/,
+ path.resolve(__dirname, 'assets/shop/controllers/ApiLoginController.js')
+ )
+ );
...
Step 3. Rebuild assets
yarn encore dev # or: yarn encore production
Reporters
We would like to extend our gratitude to the following individuals for their detailed reporting and responsible disclosure of this vulnerability: - Bartłomiej Nowiński (@bnBart)
For more information
If you have any questions or comments about this advisory:
- Open an issue in Sylius issues
- Email us at security@sylius.com
{
"affected": [
{
"database_specific": {
"last_known_affected_version_range": "\u003c= 2.0.15"
},
"package": {
"ecosystem": "Packagist",
"name": "sylius/sylius"
},
"ranges": [
{
"events": [
{
"introduced": "2.0.0"
},
{
"fixed": "2.0.16"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"database_specific": {
"last_known_affected_version_range": "\u003c= 2.1.11"
},
"package": {
"ecosystem": "Packagist",
"name": "sylius/sylius"
},
"ranges": [
{
"events": [
{
"introduced": "2.1.0"
},
{
"fixed": "2.1.12"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"database_specific": {
"last_known_affected_version_range": "\u003c= 2.2.2"
},
"package": {
"ecosystem": "Packagist",
"name": "sylius/sylius"
},
"ranges": [
{
"events": [
{
"introduced": "2.2.0"
},
{
"fixed": "2.2.3"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-31822"
],
"database_specific": {
"cwe_ids": [
"CWE-79"
],
"github_reviewed": true,
"github_reviewed_at": "2026-03-11T00:13:02Z",
"nvd_published_at": "2026-03-10T22:16:19Z",
"severity": "MODERATE"
},
"details": "### Impact\n\nA cross-site scripting (XSS) vulnerability exists in the shop checkout login form handled by the ApiLoginController Stimulus controller. \n\nWhen 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.\n\nThe message value originates from `AuthenticationException::getMessageKey()` passed through Symfony\u0027s translator (security domain, using the request locale). In the default Sylius installation, this returns a hardcoded translation key (e.g. \"Invalid credentials.\"), which is not directly user-controlled. However, using innerHTML with server-derived data violates defense-in-depth principles, and the risk escalates significantly under realistic scenarios:\n - Customized authentication handlers \u2014 if a project overrides AuthenticationFailureHandler to include user-supplied data in the message (e.g. \"No account found for \u003cusername\u003e\"), an attacker can inject arbitrary JavaScript directly via the login\n form without any privileged access.\n - Translation injection \u2014 if translation files are sourced from an untrusted database or CMS and contain HTML, the message could carry a malicious payload.\n - Man-in-the-Middle \u2014 if the response is intercepted (e.g. on HTTP or via a compromised proxy), an attacker can inject arbitrary HTML/JS into the message field.\n - Server-side injection \u2014 if any middleware, reverse proxy, or error handler modifies the JSON response body, malicious content could be injected into the message field.\n\nExploitation could lead to session hijacking, credential theft, cart/order manipulation, or phishing within the trusted shop domain.\n\nThe vulnerability affects all Sylius installations that use the default shop checkout login form with the bundled ApiLoginController.js.\n\n### Patches\nThe issue is fixed in versions: 2.0.16, 2.1.12, 2.2.3 and above.\n\n### Workarounds\nOverride the vulnerable JavaScript controller at the project level.\n\u003e Note: Step 2 differs between Sylius 2.0 and up\n\n#### Step 1. Override JavaScript controller handling login\n### Patch ApiLoginController.js\n\nCopy the original from `vendor/sylius/sylius/src/Sylius/Bundle/ShopBundle/Resources/assets/controllers/ApiLoginController.js` to `assets/shop/controllers/ApiLoginController.js` and apply:\n```diff\n...\n .then(response =\u003e {\n if (response.success) {\n window.location.reload();\n } else {\n const errorElement = this.errorPrototypeTarget.cloneNode(true);\n- errorElement.innerHtml = response.message;\n+ errorElement.textContent = response.message;\n this.errorTarget.innerHTML = errorElement.outerHTML;\n }\n })\n...\n```\n\n#### Step 2. Register the patched controller\n\u003e Sylius 2.1+ (Stimulus Bridge with `controllers.json`)\n\nDisable the vendor controller in `assets/shop/controllers.json`:\n```diff\n...\n \"api-login\": {\n- \"enabled\": true,\n+ \"enabled\": false,\n \"fetch\": \"lazy\"\n }\n...\n```\nRegister the overwritten controller in `assets/shop/bootstrap.js`\n```js\nimport ApiLoginController from \u0027./controllers/ApiLoginController\u0027\n\napp.register(\u0027sylius--shop-bundle--api-login\u0027, ApiLoginController);\n```\n---\n\u003e Sylius 2.0 (explicit imports in vendor `app.js`)\n\nUse Webpack\u0027s `NormalModuleReplacementPlugin` to swap the controller at build time. In `webpack.config.js`, after `shopConfig` is created:\n\n```diff\n+ const webpack = require(\u0027webpack\u0027);\n...\n // Shop config\n const shopConfig = SyliusShop.getWebpackConfig(path.resolve(__dirname));\n+ shopConfig.plugins.push(\n+ new webpack.NormalModuleReplacementPlugin(\n+ /\\/controllers\\/ApiLoginController\\.js$/,\n+ path.resolve(__dirname, \u0027assets/shop/controllers/ApiLoginController.js\u0027)\n+ )\n+ );\n...\n```\n\n#### Step 3. Rebuild assets\n\n```bash\nyarn encore dev # or: yarn encore production\n```\n\n### Reporters\n\nWe would like to extend our gratitude to the following individuals for their detailed reporting and responsible disclosure of this vulnerability:\n- Bart\u0142omiej Nowi\u0144ski (@bnBart)\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n- Open an issue in [Sylius issues](https://github.com/Sylius/Sylius/issues?q=sort%3Aupdated-desc+is%3Aissue+is%3Aopen)\n- Email us at [security@sylius.com](mailto:security@sylius.com)",
"id": "GHSA-vgh8-c6fp-7gcg",
"modified": "2026-03-11T20:32:40Z",
"published": "2026-03-11T00:13:02Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/Sylius/Sylius/security/advisories/GHSA-vgh8-c6fp-7gcg"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-31822"
},
{
"type": "PACKAGE",
"url": "https://github.com/Sylius/Sylius"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N",
"type": "CVSS_V4"
}
],
"summary": "Sylius has a XSS vulnerability in checkout login form"
}
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.