GHSA-6wh5-mw9h-5c3w: Shopware vulnerable to path traversal via Plugin upload
Noroxi assessment
Priority: Monitor (action score 10/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Anyone who can reach it over the internet can trigger it. Administrator privileges are required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: shopware/core (Packagist) 6.7.3.1, 6.6.10.7; shopware/platform (Packagist) 6.7.3.1, 6.6.10.7.
Low priority for now. Upgrade to shopware/core (Packagist) 6.7.3.1, 6.6.10.7; shopware/platform (Packagist) 6.7.3.1, 6.6.10.7 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: OSV
### Impact Malicious actors can exploit this vulnerability to write files within arbitrary directories on the filesystem of the Shopware web container. This could allow them to gain persistent shell access by uploading a PHP-shell file to an accessible folder. It is important to note that this vulnerability is only present on on-premises installation of Shopware and not present on the SaaS installation due to additional security checks being implemented on the uploaded plugin files. #### Description A path traversal vulnerability allows malicious actors to access files and folders that are outside the folder structure accessible to the affected function. This vulnerability occurs when an application uses unfiltered user input to point to the path of a specific file and retrieve it. This can result in gaining read/write access to sensitive information, application code, back-end systems and other (critical) files on the operating system. In certain cases, it is even possible to store arbitrary files outside the relevant directory structure on the server in order to gain access to the server. #### Applicability The Plugin upload function in use by the Shopware application is vulnerable to path traversal. Within the on-premises version of the Shopware application users are able to extend the functionality of the application by installing ‘plugins’ also referred to as ‘apps’ or ‘extensions’. These plugins can be installed using the official store or by uploading a zip file containing the required files. To prevent path traversal the Shopware application implements a check that effectively prohibits files containing ‘..’ characters from being uploaded. During review of the source code, it was noticed that the check for the prohibited characters was only performed from the third entry (index 2) of the uploaded Zip file. This means that the second entry (index 1) within the Zip file can contain path traversal characters and thus allows files to be written in directories outside of the intended plugins folder. To exploit this vulnerability, an admin account with permissions to upload plugins, is required. #### Reproduction To reproduce this vulnerability, the steps below can be followed. 1. Log in to an on-premises Shopware application with an admin account with permissions to upload plugins. 2. Create a malicious Zip file using the script provided in evidence 5. 3. Upload the generated malicious Zip file as a new plugin within the application 4. Access the filesystem of the Shopware application 5. Navigate to the path below: /var/www/html/custom/apps 6. Notice that an ‘evil.php’ file has been extracted within this folder.
- Published
- Oct 21, 2025
- Updated
- Sep 10, 2026
- EPSS
- —
- CWE
- CWE-22
Report tools
Action score
10
Low priority for now.
- CVSS
- 10 / 40 · 2.7 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · —
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| Packagist | shopware/platform | pkg:composer/shopware/platform |
| Packagist | shopware/core | pkg:composer/shopware/core |
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Packagist | shopware/core | from 6.7.0.0 · before 6.7.3.1 | 6.7.3.1 |
| Packagist | shopware/core | before 6.6.10.7 | 6.6.10.7 |
| Packagist | shopware/platform | from 6.7.0.0 · before 6.7.3.1 | 6.7.3.1 |
| Packagist | shopware/platform | before 6.6.10.7 | 6.6.10.7 |
Same product
Packagist: all recordsOther highest-scoring records for the same primary product.
- GHSA-8xv9-qcr9-ww9jAuthenticated XML External Entity Processing22Monitor
- GHSA-m895-2hj3-8cg9Shopware vulnerable to MediaVisibilityRestrictionSubscriber bypass when reading media entities by aggregating fields individually21Monitor
- GHSA-27c9-vp3w-6ww8Shopware exposes sensitive user information via CSV export mapping19Monitor
Published before and after this one in the same product
- ← EarlierGHSA-wq3r-jwrq-xg6wJun 28, 2021 · Canceling of orders not related to the logged-in user0Monitor
- ← EarlierGHSA-243q-g9j3-qf6rJun 28, 2021 · non-admin users can create integration role with administrator role0Monitor
- Later →GHSA-3cpp-fv95-mpr5Oct 21, 2025 · Shopware vulnerable to Server-Side Request Forgery (SSRF) – order invoice10Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Packagist:shopware/core | 6.6.10.7 | Package registry (OSV) |
| Packagist:shopware/core | 6.7.3.1 | Package registry (OSV) |
| Packagist:shopware/platform | 6.6.10.7 | Package registry (OSV) |
| Packagist:shopware/platform | 6.7.3.1 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Not on record for this CVE: EPSS history · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- Administrator privileges are required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- low · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- Low
- Availability impact
- None
Weakness class (CWE)
CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')CVSS vector
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N
osv
Root cause
A user-supplied file name is joined with the allowed directory, but the result is never checked to confirm it is still inside that directory.
The bug in code
The whole CWE-22 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
const file = path.join(ROOT, req.query.name);
res.sendFile(file);Fixed
const file = path.resolve(ROOT, req.query.name);
if (!file.startsWith(ROOT + path.sep)) {
return res.sendStatus(400);
}
res.sendFile(file);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Path TraversalCAPEC-126likelihood: High · Very High
- Using Slashes and URL Encoding Combined to Bypass Validation LogicCAPEC-64likelihood: High · High
- Manipulating Web Input to File System CallsCAPEC-76likelihood: High · Very High
- Using Escaped Slashes in Alternate EncodingCAPEC-78likelihood: High · High
- Using Slashes in Alternate EncodingCAPEC-79likelihood: High · High
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.