Skip to main content
CVE-2026-134371VulnerabilityPublished

Frappe 8.8.0 before 16.30.0 contains an insecure direct object reference vulnerability in the SMS Settings

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-134371· High 7.1

Not known to be exploited · CVSS 7.1 High : upgrade to 16.30.0 soon.

Data as of 21 Nov 2026, 19:43 UTC

CVSS 4.0 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.07.1
CNA (VulnCheck)CVSS 3.16.5
Patch
Available – fixed in 16.30.0
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 21 Nov 2026.

What to do

Upgrade frappe to 16.30.0.

Affected software

ProductAffectedFixed in
frappefrappeAffected
  • >=8.8.0 <16.30.0
Fixed in
  • 16.30.0
PyPIfrappepkg:pypi/frappeOther threatsAffected
  • >=8.8.0 <16.30.0
Fixed in
  • 16.30.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

If you cannot patch yet, restrict access to the SMS Settings get_contact_number API to trusted users only and monitor for suspicious access patterns related to this endpoint.

Description

Frappe versions from 8.8.0 up to but not including 16.30.0 have an insecure direct object reference vulnerability in the SMS Settings get_contact_number API. This flaw allows attackers with some privileges to retrieve phone numbers of arbitrary Contact records without proper permission checks, exposing personally identifiable information (PII). The vulnerability arises from an uncorrelated EXISTS subquery used in the endpoint.

References

Community reviews

Loading reviews…