# CVE-2024-29376: Sylius has potential Cross Site Scripting vulnerability via the "Province" field in the Checkout and Address Book > Attackers can inject malicious scripts via the Province field in the Address Book, potentially leading to session hijacking or code execution. - **Severity:** Medium 6.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 22 Apr 2024 - **Updated:** 22 Nov 2024 - **Also known as:** GHSA-7prj-9ccr-hr3q ## What is CVE-2024-29376? CVE-2024-29376 is a medium-severity cross-site scripting vulnerability in n/a, published on 22 Apr 2024. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description Sylius 1.12.13 is vulnerable to Cross Site Scripting (XSS) via the "Province" field in Address Book. Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation) ## Which versions are affected by CVE-2024-29376? 10 open source packages ship an affected version, including sylius/sylius. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `sylius/sylius` | Packagist | All versions | 1.9.12 | | `sylius/sylius` | Packagist | All versions | 1.9.12 | | `sylius/sylius` | Packagist | From 1.10.0-alpha.1 | 1.10.16 | | `sylius/sylius` | Packagist | From 1.10.0-alpha.1 | 1.10.16 | | `sylius/sylius` | Packagist | From 1.11.0-alpha.1 | 1.11.17 | | `sylius/sylius` | Packagist | From 1.11.0-alpha.1 | 1.11.17 | | `sylius/sylius` | Packagist | From 1.12.0-alpha.1 | 1.12.16 | | `sylius/sylius` | Packagist | From 1.12.0-alpha.1 | 1.12.16 | | `sylius/sylius` | Packagist | From 1.13.0-alpha.1 | 1.13.1 | | `sylius/sylius` | Packagist | From 1.13.0-alpha.1 | 1.13.1 | Products: Sylius Sylius. ## How do I fix CVE-2024-29376? Upgrade sylius/sylius to a fixed version for your release line: 1.9.12, 1.10.16, 1.11.17 or 1.12.16. ## Is CVE-2024-29376 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-29376 exists. ## Other vulnerabilities in n/a - [CVE-2026-31824](https://insights.sbomify.com/CVE-2026-31824/): Sylius has a Promotion Usage Limit Bypass via Race Condition (high 8.2) - [CVE-2024-57610](https://insights.sbomify.com/CVE-2024-57610/): Denial of service in n/a (high 7.5) - [CVE-2026-31820](https://insights.sbomify.com/CVE-2026-31820/): Sylius affected by IDOR in Cart and Checkout LiveComponents (high 7.1) - [CVE-2022-24743](https://insights.sbomify.com/CVE-2022-24743/): Insufficient Session Expiration in Sylius (high 7.1) - [CVE-2026-31819](https://insights.sbomify.com/CVE-2026-31819/): Sylius has an Open Redirect via Referer Header (medium 6.9) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-29376 and fix it if it is affected. What it is: CVE-2024-29376 is a medium-severity cross-site scripting vulnerability in n/a, published on 22 Apr 2024. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-29376 exists. Affected packages and fixed versions: - sylius/sylius (Packagist): affected all versions; fixed in 1.9.12 - sylius/sylius (Packagist): affected all versions; fixed in 1.9.12 - sylius/sylius (Packagist): affected from 1.10.0-alpha.1; fixed in 1.10.16 - sylius/sylius (Packagist): affected from 1.10.0-alpha.1; fixed in 1.10.16 - sylius/sylius (Packagist): affected from 1.11.0-alpha.1; fixed in 1.11.17 - sylius/sylius (Packagist): affected from 1.11.0-alpha.1; fixed in 1.11.17 - sylius/sylius (Packagist): affected from 1.12.0-alpha.1; fixed in 1.12.16 - sylius/sylius (Packagist): affected from 1.12.0-alpha.1; fixed in 1.12.16 - sylius/sylius (Packagist): affected from 1.13.0-alpha.1; fixed in 1.13.1 - sylius/sylius (Packagist): affected from 1.13.0-alpha.1; fixed in 1.13.1 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2024-29376/ (Markdown: https://insights.sbomify.com/CVE-2024-29376/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-29376 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-29376 - OSV: https://osv.dev/vulnerability/CVE-2024-29376 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-29376/ Summaries are generated and may contain mistakes; the official description above is the record.