CVE-2026-48009

Shopware: Admin Account Takeover via User Recovery Hash Exposure

Published Jul 17, 2026 CVSS 3.1 · 6.8 Medium EPSS < 1% KEV · Not listed
Description
Shopware is an open commerce platform. Prior to 6.6.10.18 and 6.7.10.1, a low-privilege admin user with user_recovery:read ACL can take over any admin account by triggering POST /api/_action/user/user-recovery, reading the password recovery hash through POST /api/search/user-recovery, and using PATCH /api/_action/user/user-recovery/password; the root cause is that src/Core/System/User/Recovery/UserRecoveryDefinition.php exposes the hash field through the Admin API without ApiAware(false) or ReadProtection. This issue is fixed in versions 6.6.10.18 and 6.7.10.1.

Analysis

AI-generated

Technical impact

A low‑privilege administrator with the user_recovery:read ACL can exploit the Admin API by initiating a user‑recovery action, retrieving the password recovery hash through the search endpoint, and then resetting the target administrator’s password via the recovery password endpoint. This chain allows the attacker to fully take over any admin account. The flaw originates from the hash field being exposed in the Admin API without proper ApiAware or ReadProtection controls, making it an information‑exposure vulnerability (CWE‑200) that enables complete administrative compromise.

Affected Systems

Shopware Platform and Shopware Shopware products running versions earlier than 6.6.10.18 or 6.7.10.1 are affected. The issue is fixed in the publicly released 6.6.10.18 and 6.7.10.1 releases.

Risk and Exploitability

The CVSS score of 6.8 indicates a moderate severity, though the EPSS probability is below 1%, suggesting that exploitation is low in the wild at present. The vulnerability is not listed in CISA’s KEV catalog. Attackers would need to be authenticated as a low‑privilege admin and would exploit the admin API over the network, making the vector internal but accessible to any user with the user_recovery:read ACL.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Shopware to version 6.6.10.18 or 6.7.10.1 or any later release that contains the fix.
  • Restrict or remove the user_recovery:read permission from low‑privilege administrator roles to eliminate the ability to read the recovery hash.
  • Audit and monitor API activity for recovery requests, and disable or log anomalous recovery attempts to detect potential misuse.

Generated by OpenCVE AI on July 30, 2026 at 23:55 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-8v9p-g828-v98f Shopware: Admin Account Takeover via User Recovery Hash Exposure
History
Type Values Removed Values Added
First Time appeared Shopware
Shopware platform
Shopware shopware
Vendors & Products Shopware
Shopware platform
Shopware shopware
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description Shopware is an open commerce platform. Prior to 6.6.10.18 and 6.7.10.1, a low-privilege admin user with user_recovery:read ACL can take over any admin account by triggering POST /api/_action/user/user-recovery, reading the password recovery hash through POST /api/search/user-recovery, and using PATCH /api/_action/user/user-recovery/password; the root cause is that src/Core/System/User/Recovery/UserRecoveryDefinition.php exposes the hash field through the Admin API without ApiAware(false) or ReadProtection. This issue is fixed in versions 6.6.10.18 and 6.7.10.1.
Title Shopware: Admin Account Takeover via User Recovery Hash Exposure
Weaknesses CWE-200
References
Metrics cvssV3_1

{'score': 6.8, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N'}

Weaknesses
  • CWE-200

    Exposure of Sensitive Information to an Unauthorized Actor

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Jul 17, 2026, 7:08 PM
Reserved
May 20, 2026, 5:44 PM
Status
Deferred
Published
Jul 17, 2026, 6:17 PM
Modified
Jul 17, 2026, 8:17 PM