GHSA-vgh8-c6fp-7gcg
Sylius has a XSS vulnerability in checkout login form
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Blast Radius
sylius/sylius🐘sylius/sylius🐘sylius/syliusReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
Impact
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 <username>"), 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 [email protected]
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | sylius/sylius | ≥ 2.0.0&&< 2.0.16 | 2.0.16 |
| 🐘Packagist | sylius/sylius | ≥ 2.1.0&&< 2.1.12 | 2.1.12 |
| 🐘Packagist | sylius/sylius | ≥ 2.2.0&&< 2.2.3 | 2.2.3 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for sylius/sylius. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update sylius/sylius to 2.0.16 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vgh8-c6fp-7gcg is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-vgh8-c6fp-7gcg is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-vgh8-c6fp-7gcg. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-vgh8-c6fp-7gcg in your dependencies?
O3 detects GHSA-vgh8-c6fp-7gcg across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.