# CVE-2026-125387: Faveo Helpdesk through 2.0.3 Cross-Department Ticket Tampering via TicketController


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 9 Nov 2026
- **Updated:** 10 Nov 2026
- **Also known as:** GHSA-x7f6-pmcc-xv54

## What is CVE-2026-125387?

CVE-2026-125387 is a medium-severity vulnerability in faveosuite faveo-helpdesk, published on 9 Nov 2026. 

### Official description

Faveo Helpdesk through 2.0.3 contains an authorization bypass vulnerability in TicketController that allows authenticated agents to modify tickets outside their department by referencing raw ticket IDs. Attackers can call merge-tickets, change-owner, ticket/assign and ticket/surrender endpoints to close, merge or reassign other departments' tickets and enumerate customers' ticket subjects.

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

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


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

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

## Is CVE-2026-125387 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-125387 is a medium-severity vulnerability in faveosuite faveo-helpdesk, published on 9 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-125387 in the wild and no public exploit code.

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

## Sources

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

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