# CVE-2026-92455: yshop-crm through 2.1.3 Missing Authorization via CRM Customer Messaging Endpoints

> Authenticated users can send unauthorized SMS and emails to arbitrary customers due to missing authorization checks on messaging endpoints.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/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:** 17 Sep 2026
- **Also known as:** GHSA-4mh9-9cjr-wqqp

## What is CVE-2026-92455?

CVE-2026-92455 is a medium-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 sendSms and sendMail endpoints in CrmCustomerController, allowing any authenticated back-office user to send SMS and email to arbitrary customers. Attackers can invoke POST /admin-api/crm/customer/send-sms and POST /admin-api/crm/customer/send-mail with arbitrary customerIds, templateCode, and templateParams to deliver unauthorized messages through the organization's SMS and email channels.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-92455 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-92455 is a medium-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-92455 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-92455/ (Markdown: https://insights.sbomify.com/CVE-2026-92455/index.md)
```

## Sources

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

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