# CVE-2025-64105: FOSSBilling: IDOR Vulnerability in Support Ticket Creation

> Authenticated clients can create support tickets linked to other users' orders due to missing ownership checks, potentially misleading staff actions.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:L/VA:N/SC:N/SI:L/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:** 23 Jun 2026
- **Updated:** 24 Jun 2026
- **Also known as:** GHSA-rcr8-p92p-9887

## What is CVE-2025-64105?

CVE-2025-64105 is a medium-severity missing authorization vulnerability in FOSSBilling, published on 23 Jun 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

FOSSBilling is a billing and client management system that automates invoicing, payments, and communication for online service businesses. Versions 0.6.21 through 0.7.2 are vulnerable to IDOR through the support ticket creation workflow. By manipulating rel_id when rel_type=order, an authenticated client can create a support ticket that references another client's order they do not own. The ticketCreateForClient() method accepted rel_id without verifying order ownership for non-upgrade tasks, allowing clients to link a new ticket to another client's order by crafting the request. No cron task automatically processes cancel/upgrade requests from ticket relations; staff action is required. This affects integrity and confidentiality: staff could be misled into acting on the wrong order (e.g., cancellation or upgrade requests). While there is no client-to-client order data exposure, order IDs may appear in ticket context. This issue has been fixed in version 0.8.0.

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

## Which versions are affected by CVE-2025-64105?


## How do I fix CVE-2025-64105?

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

## Is CVE-2025-64105 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-64105 and fix it if it is affected.

What it is: CVE-2025-64105 is a medium-severity missing authorization vulnerability in FOSSBilling, published on 23 Jun 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-2025-64105 in the wild and no public exploit code.

Affected product: FOSSBilling. 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-2025-64105/ (Markdown: https://insights.sbomify.com/CVE-2025-64105/index.md)
```

## Sources

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

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