# CVE-2026-111937: Frappe CRM before 1.81.2 Missing Authorization on CRM Notification Records

> Authenticated Sales Users can access, read, or delete other users' CRM Notification records due to missing permission checks.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/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:** 19 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** GHSA-4rjw-6mxx-m345, GHSA-6wh4-r87p-4qfj

## What is CVE-2026-111937?

CVE-2026-111937 is a medium-severity missing authorization vulnerability in frappe crm, published on 19 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Frappe CRM before 1.81.2 contains a missing authorization vulnerability that allows authenticated Sales Users to access other users' CRM Notification records due to absent permission hooks. Attackers can query frappe.client endpoints filtering on to_user or call mark_as_read with another user argument to read, mark read, or delete others' notifications.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-111937 being exploited?

There is no known exploitation of CVE-2026-111937 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-111937 is a medium-severity missing authorization vulnerability in frappe crm, published on 19 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-111937 in the wild and no public exploit code.

Affected product: frappe 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-111937/ (Markdown: https://insights.sbomify.com/CVE-2026-111937/index.md)
```

## Sources

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

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