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.
Published: 2026-06-23
Score: 5.1 Medium
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

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. The issue has been fixed in version 0.8.0.

Affected Systems

FOSSBilling, billing and client management platform; the affected release range is 0.6.21 through 0.7.2. Users running these versions should immediately upgrade to 0.8.0 or later to obtain the fix.

Risk and Exploitability

The CVSS score of 5.1 indicates a moderate severity. No EPSS score is available, and the vulnerability is not listed in CISA’s KEV catalog. Exploitation requires an authenticated client account and involves crafting a request to the ticket creation endpoint. Because staff must act on the resulting ticket, the risk is primarily to business integrity rather than immediate data loss, making the likelihood of widespread exploitation lower than high‑severity flaws but still significant for organizations with high‑volume ticketing.

Generated by OpenCVE AI on June 24, 2026 at 10:07 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade FOSSBilling to version 0.8.0 or later.
  • Restrict the creation of support tickets that reference orders not owned by the client, e.g., by adding ownership validation to the ticketCreateForClient() workflow or by requiring staff approval before processing ticket‑initiated order actions.
  • Perform a review of existing support tickets to identify any misassociated orders and train staff to verify order ownership before acting on ticket requests.

Generated by OpenCVE AI on June 24, 2026 at 10:07 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Tue, 23 Jun 2026 23:45:00 +0000

Type Values Removed Values Added
First Time appeared Fossbilling
Fossbilling fossbilling
Vendors & Products Fossbilling
Fossbilling fossbilling

Tue, 23 Jun 2026 20:30:00 +0000

Type Values Removed Values Added
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.
Title FOSSBilling: IDOR Vulnerability in Support Ticket Creation
Weaknesses CWE-639
References
Metrics cvssV4_0

{'score': 5.1, 'vector': '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'}


Subscriptions

Fossbilling Fossbilling
cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-06-24T13:10:21.582Z

Reserved: 2025-10-27T15:26:14.127Z

Link: CVE-2025-64105

cve-icon Vulnrichment

No data.

cve-icon NVD

No data.

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-06-24T10:15:05Z

Weaknesses
  • CWE-639

    Authorization Bypass Through User-Controlled Key