dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2026-53644

HIGH · 8.6 CVSS v4.0 Published 2026-07-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
92/100
Remediation priority · Urgent
Remotely reachable Zero-click 7 weeks old

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. Versions 0.5.3 through 0.7.2 allow authenticated clients to both read and reset API key service secrets for orders that are no longer in an `active` state (e.g., `suspended`, `canceled`). The root cause is missing order-state validation in two client API endpoints, despite an `isActive()` helper already existing in the `Serviceapikey` module and the frontend UI correctly gating access on `order.status == 'active'`. Version 0.8.0 contains a fix. Some workarounds are available. If the `Serviceapikey` module is not needed, uninstall it to remove the affected endpoints. One may also use a reverse proxy or WAF to restrict access to `/api/client/order/service` and `/api/client/serviceapikey/reset` based on application-level order-state logic.

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.5.3-0.7.2 contain a broken access control vulnerability where two client API endpoints (/api/client/order/service and /api/client/serviceapikey/reset) fail to validate order status before allowing access to API key service secrets. Despite an isActive() helper existing in the Serviceapikey module and the frontend correctly gating access on active orders, the backend API endpoints lack this validation, permitting authenticated clients to read/reset secrets for suspended or canceled orders.

MitigationUpgrade to FOSSBilling version 0.8.0 which contains the fix; alternatively, uninstall the Serviceapikey module if not needed or use a WAF/reverse proxy to restrict access to the affected endpoints based on order-state logic.

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:H/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 installed FOSSBilling version
    Check the version.php file in the FOSSBilling root directory, or look for a version indicator in the admin panel under System > Settings or About section
    Affected if Version is 0.5.3 through 0.7.2 inclusive
  2. Verify Serviceapikey module is enabled
    Navigate to the admin panel, go to Modules section, and check if the Serviceapikey module is installed and enabled
    Affected if Serviceapikey module is active
  3. Check for existing client orders
    In the admin panel, go to Orders > List Orders and identify any orders that are in suspended or canceled status, particularly for products/services that use API key functionality
    Affected if There are suspended or canceled orders present in the system
  4. Test API endpoint access control for order status
    Using an authenticated client API token, attempt to access /api/client/order/service or /api/client/serviceapikey/reset for an order in suspended or canceled status via a curl request or API client tool
    Affected if The API returns secret data or allows reset operations for inactive orders without rejecting based on order status
  5. Review API response for order status validation
    Make API calls to the affected endpoints with a valid client session but for a suspended/canceled order, and inspect whether the response includes 'order_status' or 'is_active' validation errors or actually returns service data
    Affected if API returns service secrets or allows reset for orders that are not active (status not 'active')

A system is affected if running FOSSBilling version 0.5.3-0.7.2 with the Serviceapikey module enabled, and the backend API endpoints allow access to secrets for orders that are suspended or canceled.

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 which contains the fix; alternatively, uninstall the Serviceapikey module if not needed or use a WAF/reverse proxy to restrict access to the affected endpoints based on order-state logic.

Recommended fix High confidence

FOSSBilling version 0.8.0

  1. Backup your current FOSSBilling installation and database before proceeding with any upgrade
  2. Review the official FOSSBilling upgrade documentation for your current version to ensure compatibility
  3. Upgrade FOSSBilling from versions 0.5.3-0.7.2 to version 0.8.0 which contains the fix for this vulnerability
  4. After upgrade, verify that the Serviceapikey module is properly updated and functioning
  5. Test that clients can no longer access API key secrets for orders with status other than 'active' (e.g., suspended, canceled orders)
  6. As an additional precaution, consider uninstalling the Serviceapikey module if the API key management feature is not required for your deployment
Caveat Review release notes for 0.8.0 to check for any breaking changes or deprecated features before upgrading in production environments

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-53644 — 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-53644 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