Skip to content

Shopware Vulnerable to Blind SQL-injection in DAL aggregations

High severity GitHub Reviewed Published Apr 8, 2025 in shopware/shopware • Updated May 12, 2025

Package

composer shopware/core (Composer)

Affected versions

= 6.7.0.0-rc1
>= 6.6.0.0, <= 6.6.10.2
< 6.5.8.18

Patched versions

6.7.0.0-rc2
6.6.10.3
6.5.8.18
composer shopware/platform (Composer)
= 6.7.0.0-rc1
>= 6.6.0.0, <= 6.6.10.2
< 6.5.8.18
6.7.0.0-rc2
6.6.10.3
6.5.8.18

Description

Impact

The Shopware application API contains a search functionality which enables users to search through information stored within their Shopware instance. The searches performed by this function can be aggregated using the parameters in the “aggregations”
object. The ‘name’ field in this “aggregations” in nested object is vulnerable SQL-injection and can be exploited using SQL parameters.

Patches

Update to Shopware 6.6.10.3

Workarounds

For older versions of 6.5 or 6.4 corresponding security measures are also available via a plugin. For the full range of functions, we recommend updating to the latest Shopware version.

Credit

Redteam Pentesting

References

@pweyck pweyck published to shopware/shopware Apr 8, 2025
Published to the GitHub Advisory Database Apr 8, 2025
Reviewed Apr 8, 2025
Published by the National Vulnerability Database Apr 15, 2025
Last updated May 12, 2025

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(77th percentile)

Weaknesses

CVE ID

CVE-2025-27892

GHSA ID

GHSA-8g35-7rmw-7f59

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.