https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-07T01:19:12.114176+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/euvd-2026-338582 EUVD-2026-338582 2026-10-07T01:19:12.116149+00:00 EUVD-2026-338582 https://cve.radiocsirt.org/vuln/fkie_cve-2026-48009 fkie_cve-2026-48009 2026-10-07T01:19:12.116182+00:00

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.

 https://cve.radiocsirt.org/vuln/ghsa-8v9p-g828-v98f GHSA-8v9p-g828-v98f — Shopware: Admin Account Takeover via User Recovery Hash Exposure 2026-10-07T01:19:12.116215+00:00

Affected: Packagist: shopware/platform, Packagist: shopware/core

## 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 highe…