CVE-2017-15374
No exploitation reported by the sources we read.
- Published2017-10-16
- WeaknessCWE-79
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
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.
Timeline
dates in UTC- 2017-10-1604:29CVE publishedNVD
Observed activity
isMalicious corpus · updated 2026-10-23 21:37 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2017-15374?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2017-15374?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
OSV · NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 5.x | ≥ 5.2.5, ≤ 5.3 | no fix published | OSV |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 5.2 | = 5.2.5 | no fix published | NVD |
| 5.2 | = 5.2.6 | no fix published | NVD |
| 5.2 | = 5.2.7 | no fix published | NVD |
| 5.2 | = 5.2.8 | no fix published | NVD |
| 5.2 | = 5.2.9 | no fix published | NVD |
| 5.2 | = 5.2.10 | no fix published | NVD |
| 5.2 | = 5.2.11 | no fix published | NVD |
| 5.2 | = 5.2.12 | no fix published | NVD |
| 5.2 | = 5.2.13 | no fix published | NVD |
| 5.2 | = 5.2.14 | no fix published | NVD |
| 5.2 | = 5.2.15 | no fix published | NVD |
| 5.2 | = 5.2.16 | no fix published | NVD |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
No fix published by the sources we read yet. NVD record
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- none listed PoC-in-GitHub
Sources
- NVDCVSS 3.06.1read 2026-10-23
- NVDCVSS 2.04.3read 2026-10-23
- NVDweakness (CWE)CWE-79read 2026-10-23
- FIRST EPSSEPSS score4.8 %2026-10-23
- OSVaffected packages—
Technical details
- CVSS v3 Vector
- CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
- Published
- 2017-10-16
- Last Modified
- 2026-06-17
- NVD status
- Modified
Frequently asked questions
What is CVE-2017-15374?
Is CVE-2017-15374 actively exploited?
What is the CVSS score for CVE-2017-15374?
Running shopware/shopware? Hear about its next vulnerability
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.