Quick answers
- Is CVE-2026-111937 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-111937 being exploited in the wild.
- How severe is CVE-2026-111937?
- Medium severity, with a CVSS score of 5.4, published 19 October 2026.
- Which products and versions are affected?
- Frappe Crm before 1.81.2.
- Is there a fix for CVE-2026-111937?
- Yes: fixed in 1.81.2. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-111937 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-111937?
- Check whether you run Frappe 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.
How to fix
- Fixed in: 1.81.2
Technical details
The vulnerability stems from missing authorization checks in the CRM Notification API endpoints. The mark_as_read() function accepts an arbitrary user parameter and applies modifications without validating the requester's permission to access that user's notifications. Authenticated attackers can query frappe.client endpoints with filters on to_user or invoke mark_as_read with another user's name to read, modify, or delete their notification records.
Affected products
- Frappe CRM before 1.81.2
Timeline
- 2026-10-19: disclosed