MediumGHSA-3pcr-4982-548m

Exposure of .env if project root is configured as web root in shopware/production

Published 13 Apr 2021 · Updated 10 Sept 2026

Is your project on an affected shopware/production?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected packages

Affected
<6.3.5.3
Fixed in
6.3.5.3
Update to the fixed version for your release line, for example:composer require shopware/production:^6.3.5.3
Affected
<6.3.5.3
Fixed in
6.3.5.3
Update to the fixed version for your release line, for example:composer require shopware/shopware:^6.3.5.3

Details

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

Is GHSA-3pcr-4982-548m in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected shopware/production, and gives you the command that fixes it.

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.