# CVE-2026-111939: Frappe Helpdesk before 1.26.0 Authorization Bypass via raised_by in Ticket Creation

> Authenticated users can bypass authorization to create tickets impersonating others and read their replies in Frappe Helpdesk.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 19 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** GHSA-4f8v-crcw-833x, GHSA-xf93-jjcj-44vm

## What is CVE-2026-111939?

CVE-2026-111939 is a medium-severity missing authorization vulnerability in frappe helpdesk, published on 19 Oct 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Frappe Helpdesk before 1.26.0 contains an authorization bypass vulnerability that allows authenticated portal users to create tickets impersonating other customers by supplying a raised_by value. Attackers can call the hd_ticket.api.new endpoint with a victim's email to plant phishing tickets in their portal and read their replies via get_ticket_activities.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2026-111939 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-111939 is a medium-severity missing authorization vulnerability in frappe helpdesk, published on 19 Oct 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-111939 in the wild and no public exploit code.

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

## Sources

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

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