Skip to main content
Menu
CVEs

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.

CVE-2026-134371Published November 21, 2026, updated

7.1HighCNA
Exploited
No known exploitation
Fix
Fixed in 16.30.0
Who is exposed
Specific setups only

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

Original 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.

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.

“Frappe 8.8.0 before 16.30.0 contains an insecure direct object reference vulnerability in the SMS Settings get_contact_number API”

vulncheck.com

What to do

  1. Check whether your setup matches what the bug needs.

    Frappe versions 8.8.0 up to but not including 16.30.0
  2. Upgrade to a fixed version: 16.30.0.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

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"}.

Affected versions

cve.now Index

25Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure8/25Specific setups only, reachable over the network
  • Reach10/20Affects PyPI packages
  • Severity7.1/10CVSS 7.1
  • No patch0/5No signal

What would change the score

  • Would score about 75 if added to CISA KEV
  • Would score about 70 if CISA's SSVC rates exploitation active
  • Would score about 32 if CISA's SSVC rates it automatable

Impact

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 4

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · frappe/frappe · Advisory GHSA-r8gf-89pc-pmv3
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-134371
RecordNVD · CVE-2026-134371
Other links 1
Linkvulncheck.com · advisories/frappe-8.8.0-before-16.30.0-idor-via-sms-settings-get-contact-number-api

Questions about CVE-2026-134371

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: cve.now feed data

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: vulncheck.com

Which versions are affected by CVE-2026-134371?

frappe (PyPI): from 8.8.0 before 16.30.0.

Source: cve.now feed data

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: vulncheck.com

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: vulncheck.com

No corrections so far. Something wrong on this page? Report an error.