Quick answers
- Is CVE-2026-92460 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-92460 being exploited in the wild.
- How severe is CVE-2026-92460?
- Medium severity, with a CVSS score of 6.5, published 16 September 2026.
- Which products and versions are affected?
- Yshop-Crm through 2.1.3.
- Is there a fix for CVE-2026-92460?
- 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-92460 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-92460?
- 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
This is a broken function-level authorization vulnerability in the CrmOperatelogController#getOperatelogPage method. Unlike sibling endpoints in the same controller (create, update, delete, get) which are guarded by @PreAuthorize annotations checking for crm:operatelog:* permissions, this endpoint carries no authorization decorator. The query applies no caller filter or data-scope restriction, returning the complete CRM activity trail of the entire deployment. Attackers with any valid back-office authentication can retrieve operator login names, display nicknames, client IP addresses, User-Agent strings, request URLs, action details, and customer identifiers. The vulnerability requires authenticated access but grants unauthorized access to organization-wide sensitive data. Patches are available in versions after 2.1.3.
Affected products
- yshop-crm yshop-crm through 2.1.3
Timeline
- 2026-09-16: disclosed: CVE-2026-92460 published