# CVE-2017-15374: Shopware XSS Vulnerability

> Remote attackers can inject malicious scripts into customer or order fields, leading to persistent XSS and potential admin account takeover in Shopware.

- **Severity:** Medium 6.1 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 16 Oct 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-mvrx-cmqw-2jgj

## What is CVE-2017-15374?

CVE-2017-15374 is a medium-severity cross-site scripting vulnerability in Shopware Shopware, published on 16 Oct 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Shopware v5.2.5 - v5.3 is vulnerable to cross site scripting in the customer and order section of the content management system backend modules. Remote attackers are able to inject malicious script code into the firstname, lastname, or order input fields to provoke persistent execution in the customer and orders section of the backend. The execution occurs in the administrator backend listing when processing a preview of the customers (kunden) or orders (bestellungen). The injection can be performed interactively via user registration or by manipulation of the order information inputs. The issue can be exploited by low privileged user accounts against higher privileged (admin or moderator) accounts.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2017-15374?

2 open source packages ship an affected version, including shopware/shopware. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `shopware/shopware` | Packagist | From 5.2.5 to 5.3 | None |
| `shopware/shopware` | Packagist | From 5.2.5 to 5.3 | None |

Products: Shopware Shopware.

## How do I fix CVE-2017-15374?

No fix has been published for CVE-2017-15374 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-15374 being exploited?

There is no known exploitation of CVE-2017-15374 in the wild and no public exploit code.

Public exploit code:

- Shopware 5.2.5/5.3 - Cross-Site Scripting (exploitdb)

## Other vulnerabilities in Shopware Shopware

- [CVE-2023-22731](https://insights.sbomify.com/CVE-2023-22731/): Improper Control of Generation of Code in Twig rendered views in shopware (critical 10.0)
- [CVE-2016-3109](https://insights.sbomify.com/CVE-2016-3109/): Shopware RCE Vulnerability (critical 9.8)
- [CVE-2024-22406](https://insights.sbomify.com/CVE-2024-22406/): Blind SQL-injection in DAL aggregations in Shopware (critical 9.3)
- [CVE-2021-32711](https://insights.sbomify.com/CVE-2021-32711/): Leak of information via Store-API (critical 9.1)
- [CVE-2026-31887](https://insights.sbomify.com/CVE-2026-31887/): Shopware unauthenticated data extraction possible through store-api.order endpoint (high 8.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-15374 and fix it if it is affected.

What it is: CVE-2017-15374 is a medium-severity cross-site scripting vulnerability in Shopware Shopware, published on 16 Oct 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2017-15374 in the wild and no public exploit code.

Affected packages and fixed versions:
- shopware/shopware (Packagist): affected from 5.2.5 up to 5.3; no fix listed
- shopware/shopware (Packagist): affected from 5.2.5 up to 5.3; no fix listed

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-2017-15374/ (Markdown: https://insights.sbomify.com/CVE-2017-15374/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-15374
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-15374
- OSV: https://osv.dev/vulnerability/CVE-2017-15374

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-15374/
Summaries are generated and may contain mistakes; the official description above is the record.