CVE-2026-23513: FOSSBilling: Broken Authorization in Client Transaction and Order Listings

Published Jun 23, 2026
·
Updated

FOSSBilling is a free, open-source billing and client management system. In versions 0.7.2 and prior, a query-construction flaw in client list endpoints allowed authenticated clients to bypass tenant scoping and retrieve other clients’ data. Details In ServiceTransaction::getSearchQuery() and Order\Service::getSearchQuery(), OR-based search/action filters were appended without grouping, allowing SQL operator precedence to evaluate OR clauses independently of the enforced clientid constraint. Crafted requests could therefore return records and metadata belonging to other clients, including identifiers, amounts, status, timestamps, and related fields. This issue was fixed in version 0.8.0.

Affected Software

1 affected component
fossbilling fossbilling<=0.7.2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade FOSSBilling to a version that resolves this vulnerability.

    Fixed in 0.8.0

Event History

Jun 23, 2026
CVE Published
via MITRE·08:11 PM
Data Sourced
via MITRE·08:11 PM
DescriptionWeakness
Data Sourced
via NVD·09:16 PM
DescriptionSeverityWeakness
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-23513?

The severity of CVE-2026-23513 is classified as high with a CVSS score of 7.1.

2

How do I fix CVE-2026-23513?

To fix CVE-2026-23513, upgrade to FOSSBilling version 0.8.0 or later, which addresses the broken authorization issue.

3

What is the impact of CVE-2026-23513 on FOSSBilling?

CVE-2026-23513 allows authenticated clients to bypass tenant scoping and access other clients' data.

4

Which versions of FOSSBilling are affected by CVE-2026-23513?

FOSSBilling versions 0.7.2 and prior are affected by CVE-2026-23513.

5

When was CVE-2026-23513 published?

CVE-2026-23513 was published on June 23, 2026.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203