Skip to main content
VulnerabilityPublished

CVE-2026-115720: frappe builder · Server-Side Request Forgery (SSRF)

Affects frappe builderSource CVE Database V5

0

Not known to be exploited · CVSS 5.3 Medium : upgrade to 1.36.1 when convenient.

Data as of 26 Oct 2026, 20:12 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 1.36.1
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:N/SC:L/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 26 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: 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 26 Oct 2026.

What to do

Upgrade frappe builder to 1.36.1.

Affected software

ProductAffectedFixed in
frappebuilderAffected
  • >=1.0.0 <1.36.1
Fixed in
  • 1.36.1
GitHubbuilderpkg:github/builderOther threatsAffected
  • >=1.0.0 <1.36.1
Fixed in
  • 1.36.1

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

AI-suggested

Upgrade Frappe Builder to version 1.36.1 or later, where this vulnerability is fixed. The fix addresses the improper URL validation and adds necessary permission checks. Until upgraded, restrict access to the convert_to_webp endpoint to trusted users only and consider implementing network-level controls to prevent SSRF exploitation. Since a fixed version is available, applying the official patch is the recommended remediation.

Description

Frappe Builder before 1.36.1 contains a server-side request forgery vulnerability in builder/api.py where the assert_not_private_url() guard validates only the initial hostname before callers invoke requests.get(url) with default redirect-following and no IP pinning, allowing an attacker-supplied public URL to HTTP-redirect to internal or link-local addresses the guard never validated. An authenticated attacker can call the convert_to_webp endpoint, which lacks a permission decorator, with a URL that redirects to internal targets such as cloud metadata services to perform SSRF, internal port scanning, or trigger a request-hang denial of service due to the missing timeout.

References

Community reviews

Loading reviews…