Exposure of .env if project root is configured as web root in shopware/productionGHSA-3pcr-4982-548m
GHSA-3pcr-4982-548m is a security vulnerability in shopware/production. A fix is available for shopware/production — see the affected versions and patch details below.
Real-World Exposure
shopware/production🐘shopware/shopwareReal-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
The .env and other sensitive files can be leaked if the project root and not /public is configured as the web root.
Patches
We recommend to update to the current version 6.3.5.3. You can get the update to 6.3.5.3 regularly via the Auto-Updater or directly via the download overview.
https://www.shopware.com/en/download/#shopware-6
Workarounds
You should always use /public as the web root.
For older versions of 6.1 and 6.2, corresponding security measures are also available via a plugin. For the full range of functions, we recommend updating to the latest Shopware version.
https://store.shopware.com/en/detail/index/sArticle/518463/number/Swag136939272659
For more information
https://docs.shopware.com/en/shopware-6-en/security-updates/security-update-04-2021
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | shopware/production | all versions | 6.3.5.3composer require shopware/production:^6.3.5.3 |
| 🐘Packagist | shopware/shopware | all versions | 6.3.5.3composer require shopware/shopware:^6.3.5.3 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for shopware/production, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update shopware/production to 6.3.5.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3pcr-4982-548m 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.
Frequently Asked Questions
Is GHSA-3pcr-4982-548m in your dependencies?
Find it across Packagist, including transitive dependencies.