CVE-2026-48014: Shopware: Admin API ACL Bypass in Order State Transition Endpoints ## Summary This is a vertical authorization bypass in the Admin API affecting order state…

Shopware: Admin API ACL Bypass in Order State Transition Endpoints

## Summary
This is a vertical authorization bypass in the Admin API affecting order state transition features (`/api/_action/order/{orderId}/state/{transition}` and similar transaction/delivery transition routes). The root cause is that the transition action routes do not declare required server-side ACL privileges, allowing low-privileged users to pass the authorization boundary. As a result, authenticated users without `order:update` can still change order states, causing real security impact such as operational integrity loss, automation workflow misuse, and fulfillment/settlement/support process disruption.

## Description
Shopware’s permission model requires server-side enforcement independent of UI guards. However, the dedicated order-state transition action endpoints are missing ACL metadata, so accounts without regular order update privileges can still submit transition requests that are processed by the backend. In real reproduction, the same low-privileged account receives 403 on the normal order update API, while the transition action API succeeds with 200 and updates order state in the database. The key point is that reproduction is possible through direct API calls regardless of UI access restrictions or hidden buttons. This is not a functional edge case; it is an implementation gap in authorization boundaries that enables privilege escalation behavior where a “read/limited-edit” user can control order lifecycle states.

### Expected Behavior
- Order, order-transaction, and order-delivery transition endpoints must perform explicit server-side ACL checks.
- Requests should be rejected unless the caller has the proper entity update privileges, such as `order:update`, `order_transaction:update`, or `order_delivery:update`.
- If an account gets 403 on the normal order update API, transition actions on the same protected resource should also be blocked by equivalent policy.
- Even if transit

Affected