# CVE-2026-115717: Frappe Builder before 1.36.1 SSRF via convert_to_webp


- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:N/SC:H/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-5qcg-q3jf-fjcg

## What is CVE-2026-115717?

CVE-2026-115717 is a medium-severity vulnerability in frappe builder, published on 26 Oct 2026. 

### Official description

Frappe Builder versions before 1.36.1 contain a server-side request forgery vulnerability in the convert_to_webp API endpoint, which lacks the has_page_write access control applied to similar asset-ingest handlers and performs an unprotected requests.get call that follows redirects without re-validating resolved IP addresses. A low-privilege authenticated user can supply an image_url pointing to an internal address or use DNS rebinding and open redirects to make the server fetch internal network resources or cloud metadata endpoints, with successful image responses saved to a world-readable /files/ URL enabling data exfiltration or blind probing of internal hosts.

Weakness: CWE-918 (Server-Side Request Forgery)

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


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

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

## Is CVE-2026-115717 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-115717 is a medium-severity vulnerability in frappe builder, published on 26 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-115717 in the wild and no public exploit code.

Affected product: frappe builder. 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-115717/ (Markdown: https://insights.sbomify.com/CVE-2026-115717/index.md)
```

## Sources

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

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