Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐘
🐘 Packagist
Not in CISA KEV
MEDIUM severity

Shopware: Admin Account Takeover via User Recovery Hash ExposureGHSA-8v9p-g828-v98f

MEDIUM

GHSA-8v9p-g828-v98f is a medium-severity (CVSS 6.8) Information Exposure vulnerability in shopware/platform. A fix is available for shopware/platform — see the affected versions and patch details below.

Also known asCVE-2026-48009
Published
Updated
Affected
4 pkgs
Patched
4 / 4
Exploits
None indexed
Exploitation data as of Oct 16, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

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

via FIRST.org ↗
0.5%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs38th percentile — riskier than 38% of all scored CVEsHighest risk
0.00%0.32%0.64%0.96%0.3%0.5%0.5%0.5%Aug 26Oct 26Oct 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

GHSA-8v9p-g828-v98f by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 390,400 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

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:

  1. POST /api/_action/user/user-recovery — triggers recovery, creates hash in DB (no auth required)
  2. POST /api/search/user-recovery — reads the hash (requires only user_recovery:read ACL)
  3. 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
EcosystemPackageVulnerable rangeFix
🐘Packagistshopware/platform≥ 6.7.0.0&&< 6.7.10.16.7.10.1composer require shopware/platform:^6.7.10.1
🐘Packagistshopware/platformall versions6.6.10.18composer require shopware/platform:^6.6.10.18
🐘Packagistshopware/core≥ 6.7.0.0&&< 6.7.10.16.7.10.1composer require shopware/core:^6.7.10.1
🐘Packagistshopware/coreall versions6.6.10.18composer require shopware/core:^6.6.10.18

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for shopware/platform, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. 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.

  3. Workarounds

    Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

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?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works
Shopware: Admin Account Takeover via User Recovery…