In short: Two security releases (6.7.16.1 and 6.6.10.32) close critical gaps — including around API permissions, data leakage via the Store API, and SQL injection under certain PHP/DB settings. In Shopware 6.7.16.1, a stricter API access protection applies that can affect requests from apps and integrations. In addition, Shopware has confirmed several high-priority bugs that affect cart, categories, orders, and variant import.
Brief summary
- New: Shopware 6.7.16.1 with stricter API access protection and closed security issues around media, apps, templates, Store/Admin API, and tokens.
- New: Shopware 6.6.10.32 as a security release for all 6.6 shops (including against SQL injection and insufficient authorization).
- Confirmed bugs (open): Data loss for B2B employee carts after login with expired context, wrong product assignments after moving categories until reindex, duplicate orders due to expiring cart lock, variant import corrupts configurator and creates variants incompletely.
- Next release 6.7.16.0 (date may shift): Fixes for neutral error page on DB outage, correct account type in the profile, and wishlist duplicates when duplicating a product.
New Shopware versions
- Shopware 6.7.16.1 (security update): Closes a vulnerability in API access control and enforces stricter visibility rules for fields and associations. This can affect requests from apps and integrations (Administration/Store API). In Shopware 6.8, non-visible associations will be rejected with error 400. Recommended: install 6.7.16.1; then review shop apps and interfaces and remove non-visible associations or field selections from requests.
- Shopware 6.6.10.32 (security release for the 6.6 line): Fixes several gaps (including SQL injection, insufficient authorization, API data leakage). Recommended: install 6.6.10.32.
To clarify terms:
- Storefront is the public shop UI for customers.
- The Store API is the interface for shop functions on the customer side (e.g., product listings).
- The Admin API is the management interface for integrations.
- A sales channel key protects access to the Store API.
Security
-
Uploaded media could execute malicious code (stored XSS)
- Severity: medium
- Affected versions: all versions before 6.6.10.32 or 6.7 before 6.7.16.1
- Fixed in version: 6.6.10.32 and 6.7.16.1
-
Missing permission check for pre-signed media uploads (e.g., to cloud storage)
- Severity: medium
- Affected versions: 6.7.11.0 up to before 6.7.16.1
- Fixed in version: 6.7.16.1
-
Insufficient media validation — file operations outside the media path possible
- Severity: high
- Affected versions: 6.5.7.0 up to before 6.6.10.32 and 6.7 before 6.7.16.1
- Fixed in version: 6.6.10.32 and 6.7.16.1
-
Apps could read server files (insufficient package validation)
- Severity: high
- Affected versions: >= 6.3.1.0, < 6.6.10.32; as well as 6.7 versions < 6.7.16.1
- Fixed in version: 6.6.10.32 and 6.7.16.1
-
Twig/App scripts insufficiently isolated — possible privilege escalation (Twig is Shopware’s template system; App Scripts extend it)
- Severity: high
- Affected versions: all versions before 6.6.10.32 and 6.7 before 6.7.16.1
- Fixed in version: 6.6.10.32 and 6.7.16.1
-
Critical data leak via Store API aggregations
- Severity: critical
- Affected versions: all versions before 6.6.10.32 and 6.7 before 6.7.16.1
- Fixed in version: 6.6.10.32 and 6.7.16.1
-
API access rights incomplete: sensitive data visible via Store/Admin API
- Severity: high
- Affected versions: all versions <6.6.10.32 or 6.7 <6.7.16.1
- Fixed in version: 6.6.10.32 and 6.7.16.1
-
Insufficient checks when cloning: protected data could be modified
- Severity: medium
- Affected versions: all versions <6.6.10.32 and 6.7 <6.7.16.1
- Fixed in version: 6.6.10.32 and 6.7.16.1
-
Risk on plugin upload: XML processing could read server files
- Severity: high
- Affected versions: <6.6.10.32 and 6.7 <6.7.16.1
- Fixed in version: 6.6.10.32 and 6.7.16.1
-
Integrations could illegitimately use user-specific functions (integrations are technical accesses that should differ from real user logins)
- Severity: high
- Affected versions: 6.7.2.0 up to <6.7.16.1 (6.6 not affected)
- Fixed in version: 6.7.16.1
-
Critical: installed apps could capture Admin login tokens (tokens are login proofs in the Administration)
- Severity: critical
- Affected versions: Administrations <6.6.10.32 and 6.7 <6.7.16.1
- Fixed in version: 6.6.10.32 and 6.7.16.1
-
Insufficient permission checks when managing Admin accounts
- Severity: high
- Affected versions: <6.6.10.32 and 6.7 <6.7.16.1
- Fixed in version: 6.6.10.32 and 6.7.16.1
-
Critical SQL injection via Store API on PHP 8.2/8.3 (in certain DB configurations with emulated PDO prepares)
- Severity: critical
- Affected versions: <6.6.10.32 or 6.7 <6.7.16.1 on PHP 8.2/8.3 with emulated PDO prepares enabled
- Fixed in version: 6.6.10.32 and 6.7.16.1
Known issues confirmed by Shopware
-
B2B employees lose saved cart after login with expired context
- Affected: B2B employees who log in after the sales-channel context expired; the previously saved customer cart is deleted, only the previous guest cart remains. Business Partner logins are not affected.
- Status: confirmed by Shopware, priority high, open.
-
Wrong product assignments after moving categories until reindex
- Affected: All shops that move a category to a different parent node; product-category trees remain stale. Listings and filters show incorrect results until reindex (Storefront, Store API, MySQL/OpenSearch).
- Status: confirmed by Shopware, priority high, open.
- Storefront here is the public shop UI; the Store API is the corresponding customer interface.
-
Duplicate orders possible: cart lock expires after 5 seconds
- Affected: Setups with a lock store with expiration, e.g., Redis, database or Memcached — especially in multi-server environments. After the 5-second lock expires, a second submit attempt can create a second order.
- Status: confirmed by Shopware, priority high, open.
-
Product import (column "variants") corrupts configurator and creates variants incompletely
- Affected: CSV imports via the "variants" column in Administration and command line; configurator settings of previously imported products are overwritten or removed. In batch imports, variants are created only for the first product of the batch.
- Status: confirmed by Shopware, priority high, open.
Fixed, coming with the next update
-
On database outage, the Storefront shows sensitive connection data in the JSON error
- Status: fix merged, expected with 6.7.16.0.
-
Business customer account is incorrectly displayed as "Private" in the profile and switched
- Status: fix merged, expected with 6.7.16.0.
-
When duplicating a product, customer wishlists are copied
- Status: fix merged, expected with 6.7.16.0.
Outlook for Shopware 6.7.16.0
According to GitHub, the following changes are already completed and assigned to milestone 6.7.16.0 (planned for 02/11/2026). Dates can shift. Only completed changes are listed:
- Neutral error page instead of JSON output with connection data when the database is not reachable.
- Correction of display and storage of the account type in the customer profile, so that a business account does not incorrectly appear as "Private" or get switched.
- Prevent wishlist duplicates: when duplicating a product, existing wishlist entries are no longer carried over.
Frequently asked questions
Do I need to update to Shopware 6.7.16.1 or 6.6.10.32 immediately?
Yes. Both releases are security updates and close multiple gaps. In 6.7.16.1, a stricter API access protection is also enforced, which can affect integrations.
Does the stricter API access affect my apps and integrations?
Yes, potentially. Shopware 6.7.16.1 enforces stricter visibility rules for fields and associations. In 6.8, non-visible associations will be rejected with error 400. You should test apps and interfaces after the update and remove non-visible fields/associations from requests.
Am I affected by the SQL injection?
Affected are installations <6.6.10.32 or <6.7.16.1 on PHP 8.2/8.3 with emulated PDO prepares enabled (depending on database configuration). Strongly recommended: update to 6.6.10.32 or 6.7.16.1; if that is not possible short term, switch to PHP 8.4 or restrict Store API aggregations.
What is the status of the cart, category, order, and variant import issues?
These issues are confirmed by Shopware, high priority, currently open. The sources list operational measures until they are fixed (e.g., reindex after moving categories, avoid variant import via "variants" for now).
What should you do now?
- Install security updates promptly:
- Update Shopware 6.7 to 6.7.16.1.
- Update Shopware 6.6 to 6.6.10.32.
- After updating to 6.7.16.1, check apps and integrations:
- Review requests via Administration/Store API and remove non-visible fields/associations from requests.
- Review permissions and integrations:
- Check integration and app permissions, especially around user/account management, create/clone actions, and access to customer/order data.
- Consider media and upload security until all updates are in place:
- If not updated yet: disable public HTML uploads and review existing media.
- If you use pre-signed uploads and are not on 6.7.16.1 yet: expose upload endpoints only to trusted callers.
- If an immediate update is not possible, apply temporary measures:
- For SQL injection risk (PHP 8.2/8.3 with emulated PDO prepares): according to the source, switch to PHP 8.4 or restrict Store API aggregations until the update is done.
- Work around confirmed bugs until fixes are available:
- B2B cart: inform employees; if possible, log in before shopping; secure important carts/quotes; inform partners/support.
- Moving categories: after reparenting, start a full product reindex and review affected listings and SEO outputs.
- Duplicate orders: clarify with hosting/agency whether an expiring lock store is used; monitor checkout for duplicate orders and use temporary measures such as button blocking/notice.
- Variant import: avoid imports via the "variants" column for now; check existing products/variants; pause imports or process individually without batching and plan a backup before changes.
- Keep an eye on the next release:
- The fixes for neutral error messages on DB outage, account type in profile, and wishlists on product duplication are expected with 6.7.16.0. Plan the update as soon as it is available.
— Author: Stefan Pilz, Shopware freelancer
Sources
- New version: Security update 6.7.16.1 with stricter API access protection
- New version: Security update 6.6.10.32 for the 6.6 line
- Security: Uploaded media could execute malicious code (stored XSS)
- Security: Missing permission check for pre-signed media uploads
- Security: Insufficient media validation — file operations outside the media path possible
- Security: Apps could read server files (insufficient package validation)
- Security: Twig/App scripts insufficiently isolated — possible privilege escalation
- Security: Critical data leak via Store API aggregations
- Security: API access rights incomplete: sensitive data visible via Store/Admin API
- Security: Insufficient checks when cloning: protected data could be modified
- Security: Risk on plugin upload: XML processing could read server files
- Security: Integrations could illegitimately use user-specific functions
- Security: Critical: installed apps could capture Admin login tokens
- Security: Insufficient permission checks when managing Admin accounts
- Security: Critical SQL injection via Store API on PHP 8.2/8.3
- Known issue: B2B employees lose saved cart after login with expired context
- Known issue: Wrong product assignments after moving categories until reindex
- Known issue: Duplicate orders possible: cart lock expires after 5 seconds
- Known issue: Product import (column "variants") corrupts configurator and creates variants incompletely
- Fixed: Security plugin 2.0.26 can completely break Shopware 6.5.2.1 (500 error)
- Fixed: Security plugin 2.0.26 causes 500 error under Shopware 6.5.2.1
- Fixed: Security plugin 2.0.25 can break the Storefront with Twig 3.20.0
- Fixed: On DB outage, Storefront shows sensitive connection data in JSON error
- Fixed: Business customer account is incorrectly displayed as "Private" in profile and switched
- Fixed: When duplicating a product, customer wishlists are copied