# CVE-2026-116492: Frappe CRM before 1.89.1 Missing Authorization via Phone Lookup API


- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 26 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** GHSA-qmcv-7jcv-gffw

## What is CVE-2026-116492?

CVE-2026-116492 is a high-severity vulnerability in frappe crm, published on 26 Oct 2026. 

### Official description

Frappe CRM app before 1.89.1 contains a missing authorization vulnerability that allows authenticated low-privileged users to read CRM Lead records they are not permitted to access by querying the get_contact_by_phone_number API, which performs raw database queries without invoking the permission system. Attackers can supply a known phone number to the crm.integrations.api.get_contact_by_phone_number endpoint to retrieve full lead details otherwise blocked by standard API and UI access controls, resulting in unauthorized disclosure of sensitive CRM data.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-116492 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-116492 is a high-severity vulnerability in frappe crm, published on 26 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-116492 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-116492/ (Markdown: https://insights.sbomify.com/CVE-2026-116492/index.md)
```

## Sources

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

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