CVE-2026-53644: FOSSBilling's missing order-state validation allows clients to read and reset API key secrets for non-active orders

Published Jul 6, 2026
·
Updated

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.

Affected Software

2 affected components
fossbilling fossbilling>=0.5.3<=0.7.2
fossbilling fossbilling=0.8.0

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
  2. Remove

    Remove FOSSBilling (Serviceapikey module) from your environment.

    If the `Serviceapikey` module is not needed, uninstall it to remove the affected endpoints (`/api/client/serviceapikey/reset` and related service API functionality).

  3. Compensating control

    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 (only allow when the order is active, matching the frontend gating `order.status == 'active'`).

Event History

Jul 6, 2026
CVE Published
via MITRE·10:51 PM
Data Sourced
via MITRE·10:51 PM
DescriptionWeakness
Data Sourced
via NVD·11: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-53644?

CVE-2026-53644 has a risk rating of 52, indicating a moderate severity level.

2

How do I fix CVE-2026-53644?

To fix CVE-2026-53644, update FOSSBilling to version 0.7.3 or later, where the issue with order-state validation is addressed.

3

What types of orders are affected by CVE-2026-53644?

CVE-2026-53644 affects non-active orders, including those that are suspended or canceled.

4

Who is vulnerable to CVE-2026-53644?

Authenticated clients using FOSSBilling versions 0.5.3 through 0.7.2 are vulnerable to CVE-2026-53644.

5

What consequences can occur due to CVE-2026-53644?

Due to CVE-2026-53644, clients may exploit the vulnerability to read and reset API key secrets for non-active orders, compromising security.

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