GHSA-8v9p-g828-v98f
MEDIUMGHSA-8v9p-g828-v98f is a medium-severity (CVSS 6.8) Information Exposure vulnerability in shopware/platform. O3 Security confirms whether GHSA-8v9p-g828-v98f is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Shopware: Admin Account Takeover via User Recovery Hash Exposure
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-8v9p-g828-v98f.
EPSS Exploitation Probability
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.
How urgent is this, really
GHSA-8v9p-g828-v98f plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 0 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
shopware/platform🐘shopware/platform🐘shopware/core🐘shopware/coreReal-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
Summary
A low-privilege admin user with user_recovery:read ACL can take over any admin account. The attacker triggers password recovery for the victim (unauthenticated endpoint), reads the recovery hash from the Admin API search endpoint, then uses the hash to reset the victim's password (another unauthenticated endpoint). The recovery hash — intended to be secret and delivered only via email — is fully readable through the standard entity search API.
OWASP: A01:2021 — Broken Access Control
Root Cause
The user_recovery entity exposes its hash field through the Admin API search endpoint (POST /api/search/user-recovery). The hash field lacks ApiAware(false) or ReadProtection, so any user with user_recovery:read ACL can read it.
The password recovery flow assumes the hash is delivered exclusively via email. The Admin API provides an alternative channel to obtain it, breaking this assumption.
Three endpoints combine to form the attack:
POST /api/_action/user/user-recovery— triggers recovery, creates hash in DB (no auth required)POST /api/search/user-recovery— reads the hash (requires onlyuser_recovery:readACL)PATCH /api/_action/user/user-recovery/password— resets password using hash (no auth required)
Vulnerable code:
src/Core/System/User/Recovery/UserRecoveryDefinition.php—hashfield isApiAwarewith noReadProtection
Impact
- Full admin account takeover — attacker gains the highest privilege level in the system
- All admin capabilities — user/role management, system configuration, plugin management, customer data access
- Cascading compromise — taken-over admin account can be used to pivot to other attacks
- Low barrier —
user_recovery:readis a seemingly harmless permission that grants devastating access
Remediation
Remove the hash field from API responses:
// src/Core/System/User/Recovery/UserRecoveryDefinition.php
(new StringField('hash', 'hash'))
->addFlags(new Required(), new ApiAware(false)),
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | shopware/platform | ≥ 6.7.0.0&&< 6.7.10.1 | 6.7.10.1 |
| 🐘Packagist | shopware/platform | all versions | 6.6.10.18 |
| 🐘Packagist | shopware/core | ≥ 6.7.0.0&&< 6.7.10.1 | 6.7.10.1 |
| 🐘Packagist | shopware/core | all versions | 6.6.10.18 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for shopware/platform. 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/platform to 6.7.10.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8v9p-g828-v98f 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 GHSA-8v9p-g828-v98f 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 GHSA-8v9p-g828-v98f. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-8v9p-g828-v98f in your dependencies?
O3 detects GHSA-8v9p-g828-v98f across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.