---
title: "CVE-2026-92456: yshop-crm - Broken Access Control"
description: "yshop-crm through 2.1.3 contains a broken access control vulnerability caused by lack of authorization enforcement on saveRedisSet and getRedisSet endpoints in CrmCustomerController, letting authenticated back-office users read and modify lead-allocation and customer auto-recycling policies, exploit requires authenticated back-office user access."
url: https://panop.io/threat-heartbeat/CVE-2026-92456/
---

# CVE-2026-92456 yshop-crm - Broken Access Control

yshop-crm through 2.1.3 contains a broken access control vulnerability caused by lack of authorization enforcement on saveRedisSet and getRedisSet endpoints in CrmCustomerController, letting authenticated back-office users read and modify lead-allocation and customer auto-recycling policies, exploit requires authenticated back-office user access.

CVSS base score 7.1 /10

High

CISA KEV

Not listed

Public exploit

None known

Authentication

Required

EPSS

0.50% chance of exploitation in 30 days

[View the NVD record ↗](https://nvd.nist.gov/vuln/detail/CVE-2026-92456)

## Details

Type

Broken Access Control

Impact

Data Tampering

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L

Published

16 September 2026

Updated

15 October 2026

Weakness

[CWE-862](https://cwe.mitre.org/data/definitions/862.html)

## Vendor fix

Update to the latest version beyond 2.1.3 that enforces proper authorization.

Patching closes this CVE. It does not tell you which of your systems run the affected version, or what else is exposed alongside them.

## References

- [https://nvd.nist.gov/vuln/detail/CVE-2026-92456](https://nvd.nist.gov/vuln/detail/CVE-2026-92456)
- [https://github.com/LinYuanyi1/cve-request-poc/blob/master/yshop-crm/C04\_crm\_customer\_save\_redis\_set.py](https://github.com/LinYuanyi1/cve-request-poc/blob/master/yshop-crm/C04_crm_customer_save_redis_set.py)
- [https://github.com/guchengwuyue/yshop-crm](https://github.com/guchengwuyue/yshop-crm)
- [https://github.com/guchengwuyue/yshop-crm/blob/5f5810a0e1e4ab0828523ec299bf973c2f9065d7/yshop-crm/pom.xml#L30](https://github.com/guchengwuyue/yshop-crm/blob/5f5810a0e1e4ab0828523ec299bf973c2f9065d7/yshop-crm/pom.xml#L30)
- [https://github.com/guchengwuyue/yshop-crm/blob/5f5810a0e1e4ab0828523ec299bf973c2f9065d7/yshop-crm/yshop-module-crm/yshop-module-crm-biz/src/main/java/co/yixiang/yshop/module/crm/controller/admin/crmcustomer/CrmCustomerController.java#L136](https://github.com/guchengwuyue/yshop-crm/blob/5f5810a0e1e4ab0828523ec299bf973c2f9065d7/yshop-crm/yshop-module-crm/yshop-module-crm-biz/src/main/java/co/yixiang/yshop/module/crm/controller/admin/crmcustomer/CrmCustomerController.java#L136)
- [https://github.com/guchengwuyue/yshop-crm/blob/5f5810a0e1e4ab0828523ec299bf973c2f9065d7/yshop-crm/yshop-module-crm/yshop-module-crm-biz/src/main/java/co/yixiang/yshop/module/crm/job/CustomerAutoJob.java#L34](https://github.com/guchengwuyue/yshop-crm/blob/5f5810a0e1e4ab0828523ec299bf973c2f9065d7/yshop-crm/yshop-module-crm/yshop-module-crm-biz/src/main/java/co/yixiang/yshop/module/crm/job/CustomerAutoJob.java#L34)
- [https://github.com/guchengwuyue/yshop-crm/blob/5f5810a0e1e4ab0828523ec299bf973c2f9065d7/yshop-crm/yshop-module-crm/yshop-module-crm-biz/src/main/java/co/yixiang/yshop/module/crm/service/crmcustomer/CrmCustomerServiceImpl.java#L160](https://github.com/guchengwuyue/yshop-crm/blob/5f5810a0e1e4ab0828523ec299bf973c2f9065d7/yshop-crm/yshop-module-crm/yshop-module-crm-biz/src/main/java/co/yixiang/yshop/module/crm/service/crmcustomer/CrmCustomerServiceImpl.java#L160)
- [https://www.vulncheck.com/advisories/yshop-crm-through-2.1.3-missing-authorization-via-crm-customer-rule-configuration-endpoints](https://www.vulncheck.com/advisories/yshop-crm-through-2.1.3-missing-authorization-via-crm-customer-rule-configuration-endpoints)

[← All CVEs](https://panop.io/threat-heartbeat/)

## What this record can't tell you

- Whether you run the affected software, and where
- Whether an attacker can actually reach and exploit it
- The misconfigurations that never get a CVE number
- What it would cost the business, ranked into what to fix first

Panop answers these inside your environment, for this CVE and every other finding.

[Book a demo](https://panop.io/demo)