Description
yshop-crm through 2.1.3 fails to enforce authorization on the saveRedisSet and getRedisSet endpoints in CrmCustomerController, allowing any authenticated back-office user to read and modify installation-wide lead-allocation and customer auto-recycling policy. Attackers can invoke these endpoints to manipulate shared Redis keys controlling customer auto-recycling behavior, causing mass customer data deletion, disabling lead recycling, or blocking customer creation across the deployment.
Affected products
| Vendor | Product | Affected | Fixed |
|---|---|---|---|
| guchengwuyue | yshop-crm | ≤ 2.1.3 | — |
References
- Reporter proof of concept: unauthorized policy rewrite via /crm/customer/saveRedisSet exploit
- saveRedisSet declared without @PreAuthorize and writing three Redis keys at 2.1.3 technical-description
- CustomerAutoJob consumes notRecordDay and notSuccessDay to recycle customers technical-description
- openCustomer nulls customer ownership and deletes follow-up records technical-description
- Maven revision property showing the affected tree is version 2.1.3 technical-description
- yshop-crm source repository product
- VulnCheck Advisory: yshop-crm through 2.1.3 Missing Authorization via CRM Customer Rule-Configuration Endpoints third-party-advisory