How severe is CVE-2025-27892?

CVE-2025-27892 has a CVSS score of 6.8/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2025-27892?

CVE-2025-27892 affects the following packages: shopware/core (Packagist), shopware/platform (Packagist), shopware/core (Packagist), shopware/platform (Packagist), shopware/core (Packagist), shopware/platform (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2025-27892?

Update shopware/core to 6.7.0.0-rc2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-27892 is resolved across your whole dependency graph.

How do I detect CVE-2025-27892 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for shopware/core. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate CVE-2025-27892 if there is no patch (or I can't update yet)?

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 does O3 Security protect against CVE-2025-27892?

O3 pinpoints whether CVE-2025-27892 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is CVE-2025-27892 actively exploited in the wild?

No public exploit code has been indexed for CVE-2025-27892 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2025-27892?

CVE-2025-27892 has an EPSS (Exploit Prediction Scoring System) score of 11.4%, placing it in the 95th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score warrants monitoring and prompt remediation.

Is there exploit tooling available for CVE-2025-27892?

A Nuclei detection template exists for CVE-2025-27892, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2025-27892 published, and has it been updated?

CVE-2025-27892 was published on April 15, 2025 and was last updated on March 12, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

CVE-2025-27892

MEDIUM

Shopware Vulnerable to Blind SQL-injection in DAL aggregations

Also known asGHSA-8g35-7rmw-7f59

Published

Apr 15, 2025

Updated

Mar 12, 2026

Affected

6 pkgs

Patched

6 / 6

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

11.4%probability of exploitation in next 30 days

Moderate Risk95th percentile+10.16%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

6 pkgs affected

🐘shopware/core🐘shopware/platform🐘shopware/core🐘shopware/platform🐘shopware/core🐘shopware/platform

Real-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

Shopware prior to version 6.5.8.13 is affected by a SQL injection vulnerability in the /api/search/order endpoint. NOTE: this issue exists because of a CVE-2024-22406 and CVE-2024-42357 regression.

Affected Packages

6 total 6 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`shopware/core`	≥ 6.7.0.0-rc1&&< 6.7.0.0-rc2	6.7.0.0-rc2
🐘Packagist	`shopware/platform`	≥ 6.7.0.0-rc1&&< 6.7.0.0-rc2	6.7.0.0-rc2
🐘Packagist	`shopware/core`	≥ 6.6.0.0&&< 6.6.10.3	6.6.10.3
🐘Packagist	`shopware/platform`	≥ 6.6.0.0&&< 6.6.10.3	6.6.10.3
🐘Packagist	`shopware/core`	all versions	6.5.8.18
🐘Packagist	`shopware/platform`	all versions	6.5.8.18

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for shopware/core. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update shopware/core to 6.7.0.0-rc2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-27892 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 pinpoints whether CVE-2025-27892 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2025-27892. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Shopware prior to version 6.5.8.13 is affected by a SQL injection vulnerability in the /api/search/order endpoint. NOTE: this issue exists because of a CVE-2024-22406 and CVE-2024-42357 regression.

O3 Security · Impact-Aware SCA

Is CVE-2025-27892 in your dependencies?

O3 detects CVE-2025-27892 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works