# CVE-2026-115718: Frappe Builder 1.33.0 before 1.36.0 Missing Authorization via improve_prompt


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/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-58mj-c563-p78w

## What is CVE-2026-115718?

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

### Official description

Frappe Builder versions 1.33.0 before1.36.0 contain a missing authorization vulnerability in the improve_prompt endpoint that allows any authenticated non-Guest session to invoke LLM completions without proper permission checks. Attackers can call the improve_prompt API to leverage the site owner's stored OpenRouter API key via resolve_api_key, consuming paid LLM credits and effectively turning the site into a free LLM proxy.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-115718 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-115718 is a medium-severity vulnerability in frappe builder, published on 26 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-115718 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-115718/ (Markdown: https://insights.sbomify.com/CVE-2026-115718/index.md)
```

## Sources

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

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