How severe is GHSA-8v9p-g828-v98f?

GHSA-8v9p-g828-v98f 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 GHSA-8v9p-g828-v98f?

GHSA-8v9p-g828-v98f affects the following packages: shopware/platform (Packagist), shopware/platform (Packagist), shopware/core (Packagist), shopware/core (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-8v9p-g828-v98f?

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.

How do I detect GHSA-8v9p-g828-v98f in my Packagist dependencies?

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.

How do I mitigate GHSA-8v9p-g828-v98f 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 GHSA-8v9p-g828-v98f?

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.

Is GHSA-8v9p-g828-v98f actively exploited in the wild?

No public exploit code has been indexed for GHSA-8v9p-g828-v98f 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 GHSA-8v9p-g828-v98f?

GHSA-8v9p-g828-v98f has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 19th 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 indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-8v9p-g828-v98f?

GHSA-8v9p-g828-v98f is classified as Information Exposure (CWE-200). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-8v9p-g828-v98f published, and has it been updated?

GHSA-8v9p-g828-v98f was published on June 4, 2026 and was last updated on June 4, 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

GHSA-8v9p-g828-v98f

MEDIUM

Shopware: Admin Account Takeover via User Recovery Hash Exposure

Also known asCVE-2026-48009

Published

Jun 4, 2026

Updated

Jun 4, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk19th percentile0.00%

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

4 pkgs affected

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

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

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 only user_recovery:read ACL)
PATCH /api/_action/user/user-recovery/password — resets password using hash (no auth required)

Vulnerable code:

src/Core/System/User/Recovery/UserRecoveryDefinition.php — hash field is ApiAware with no ReadProtection

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:read is 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

4 total 4 fixed

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 dependency

Detect
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

## 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 sea

O3 Security · Impact-Aware SCA

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.

Scan my dependencies How O3 SCA works