# CVE-2026-92456: yshop-crm through 2.1.3 Missing Authorization via CRM Customer Rule-Configuration Endpoints

> Authenticated users can manipulate CRM customer rules via unprotected endpoints, causing mass data deletion or blocking customer creation.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Sep 2026
- **Updated:** 16 Sep 2026
- **Also known as:** GHSA-chh2-hwpm-2mcg

## What is CVE-2026-92456?

CVE-2026-92456 is a high-severity missing authorization vulnerability in guchengwuyue yshop-crm, published on 16 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-92456?


## How do I fix CVE-2026-92456?

No fix has been published for CVE-2026-92456 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-92456 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-92456 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-92456 and fix it if it is affected.

What it is: CVE-2026-92456 is a high-severity missing authorization vulnerability in guchengwuyue yshop-crm, published on 16 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-92456 exists.

Affected product: guchengwuyue yshop-crm. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-92456/ (Markdown: https://insights.sbomify.com/CVE-2026-92456/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-92456
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-92456
- OSV: https://osv.dev/vulnerability/CVE-2026-92456

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-92456/
Summaries are generated and may contain mistakes; the official description above is the record.