dbcve.org
Incorrect AuthorizationWeakness · CWE-863

CVE-2026-23513

HIGH · 7.1 CVSS v4.0 Published 2026-06-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 client_id 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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

FOSSBilling versions 0.7.2 and prior contain an IDOR vulnerability in ServiceTransaction::getSearchQuery() and Order\Service::getSearchQuery() where OR-based search filters were appended without proper SQL grouping. This causes the enforced client_id constraint to be evaluated independently of OR clauses due to SQL operator precedence, allowing authenticated clients to retrieve data belonging to other tenants via crafted requests.

MitigationUpgrade to FOSSBilling version 0.8.0 or later, which contains the fix for proper SQL clause grouping to ensure the client_id constraint is always enforced within the correct logical group.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify FOSSBilling installation and version
    Locate the FOSSBilling installation directory. Check for a composer.json file or config/version.php to find the installed version number. Common paths include /var/www/fossbilling or similar web root directories.
    Affected if The installed version is 0.7.2 or any version prior to 0.7.2 (e.g., 0.7.1, 0.7.0, 0.6.x).
  2. Locate vulnerable method files
    Search for the files containing ServiceTransaction::getSearchQuery() and Order\Service::getSearchQuery() in the src directory. Typical path: src/Model/ServiceTransaction.php and src/Model/Order/Service.php.
    Affected if These files exist in the installation and the version is 0.7.2 or prior.
  3. Verify API endpoint availability
    Check if the API endpoints that invoke these search methods are accessible. FOSSBilling typically exposes API at /api/index.php or similar. Look for transaction and order listing endpoints that accept search parameters.
    Affected if The API is accessible and accepts client authentication tokens.
  4. Confirm multi-tenant configuration
    Determine if the installation serves multiple clients/tenants. Check configuration for multiple client accounts or reseller setups. Look in the database for multiple client_id records.
    Affected if The installation has multiple client accounts and uses the transaction/order search functionality.

A user is affected if FOSSBilling version 0.7.2 or prior is installed, the system has multiple client accounts, and the API endpoints for transaction or order searches are accessible to authenticated clients.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to FOSSBilling version 0.8.0 or later, which contains the fix for proper SQL clause grouping to ensure the client_id constraint is always enforced within the correct logical group.

Recommended fix High confidence

0.8.0

  1. 1. Backup your current FOSSBilling installation and database before proceeding with any upgrade.
  2. 2. Download FOSSBilling version 0.8.0 from the official GitHub repository (github.com/FOSSBilling/FOSSBilling).
  3. 3. Review the upgrade instructions in the project's documentation for migrating from 0.7.x to 0.8.0.
  4. 4. Replace the existing installation files with the new version 0.8.0 files.
  5. 5. Run any database migration scripts provided in the upgrade package.
  6. 6. Verify that the vulnerability is resolved by testing that client users can no longer access other clients' transaction or order data.
  7. 7. Confirm all functionality works as expected after the upgrade.
Caveat Review release notes for version 0.8.0 to check for any breaking changes or required configuration updates before deploying to production.

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-23513 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-23513 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data