CVE-2026-92456: yshop-crm authorization bypass in CrmCustomerController

CVE-2026-92456 · Severity: high · CVSS 7.1 · Published 2026-09-16

yshop-crm is a CRM system for sales teams that manages customer data, lead allocation, and customer recycling policies. The system fails to properly restrict access to two critical API endpoints, allowing any authenticated user to read and modify installation-wide settings that control how customers are distributed to salespeople and automatically recycled. An attacker can manipulate these settings to delete customer records in bulk, disable lead recycling, or prevent new customer creation across the entire deployment.

Technologies: Yshop-Crm. Vendors: Yshop-Crm.

Quick answers

Is CVE-2026-92456 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-92456 being exploited in the wild.
How severe is CVE-2026-92456?
High severity, with a CVSS score of 7.1, published 16 September 2026.
Which products and versions are affected?
Yshop-Crm through 2.1.3.
Is there a fix for CVE-2026-92456?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-92456 attacked?
It is attacked over the network.
Am I affected by CVE-2026-92456?
Check whether you run Yshop-Crm at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The vulnerability is a broken function-level authorization (CWE-639) in the CrmCustomerController class. The saveRedisSet and getRedisSet endpoints lack @PreAuthorize annotations that guard sibling methods in the same controller, allowing any authenticated back-office user to invoke them without permission checks. These endpoints read and write three global Redis keys (customerNum, notRecordDay, notSuccessDay) that control customer holding limits and auto-recycling thresholds applied across the entire deployment. An attacker can modify these keys via POST /admin-api/crm/customer/saveRedisSet to manipulate lead allocation and trigger mass customer data deletion through the CustomerAutoJob scheduler. The attack requires only valid authentication credentials with minimal privilege; no network or user interaction preconditions beyond login.

Affected products

  • yshop-crm yshop-crm through 2.1.3

Timeline

  • 2026-09-16: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.