GHSA-6wh5-mw9h-5c3w is a low-severity (CVSS 2.7) vulnerability in shopware/platform. A fix is available for shopware/platform — see the affected versions and patch details below.
Shopware vulnerable to path traversal via Plugin upload
Real-World Exposure
shopware/platform🐘shopware/platform🐘shopware/core🐘shopware/coreReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
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.
- Log in to an on-premises Shopware application with an admin account with permissions to upload plugins.
- Create a malicious Zip file using the script provided in evidence 5.
- Upload the generated malicious Zip file as a new plugin within the application
- Access the filesystem of the Shopware application
- Navigate to the path below: /var/www/html/custom/apps
- Notice that an ‘evil.php’ file has been extracted within this folder.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | shopware/platform | ≥ 6.7.0.0&&< 6.7.3.1 | 6.7.3.1composer require shopware/platform:^6.7.3.1 |
| 🐘Packagist | shopware/platform | all versions | 6.6.10.7composer require shopware/platform:^6.6.10.7 |
| 🐘Packagist | shopware/core | ≥ 6.7.0.0&&< 6.7.3.1 | 6.7.3.1composer require shopware/core:^6.7.3.1 |
| 🐘Packagist | shopware/core | all versions | 6.6.10.7composer require shopware/core:^6.6.10.7 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for shopware/platform, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update shopware/platform to 6.7.3.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6wh5-mw9h-5c3w is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-6wh5-mw9h-5c3w can be triaged on real exposure rather than presence alone.
Tailored to GHSA-6wh5-mw9h-5c3w. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-6wh5-mw9h-5c3w in your dependencies?
O3 Security finds GHSA-6wh5-mw9h-5c3w across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.