CVE-2026-53648: FOSSBilling: Downloadable product files can be overwritten through filename collisions

Published Jul 6, 2026
·
Updated

FOSSBilling is a free, open-source billing and client management system. Prior to version 0.8.1, downloadable product files are stored using a deterministic filename-derived path. When an administrator uploads a file for a downloadable product, FOSSBilling stores the file as md5(<original filename>) under the uploads directory. Because the stored path depends only on the client-supplied filename, two different downloadable products, or product/order files, uploaded with the same original filename will resolve to the same stored file path. A later upload can overwrite an earlier upload, causing customers or administrators downloading the earlier product to receive the later file instead. Version 0.8.1 patches the issue. Some workarounds are available. Restrict the servicedownloadable.manage permission to fully trusted administrators only. As an operational mitigation, ensure downloadable product files use unique filenames before upload. This reduces accidental collisions but does not fully address the underlying issue.

Affected Software

1 affected component
fossbilling fossbilling<0.8.1

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.1
  2. Configuration

    Restrict the `servicedownloadable.manage` permission to fully trusted administrators only.

    FOSSBilling permissions servicedownloadable.manage = fully trusted administrators only
  3. Operational

    As an operational mitigation, ensure downloadable product files use unique filenames before upload to prevent filename collisions (since stored path is derived from the client-supplied filename and later uploads can overwrite earlier ones).

Event History

Jul 6, 2026
CVE Published
via MITRE·11:12 PM
Data Sourced
via MITRE·11:12 PM
DescriptionWeakness
Jul 7, 2026
Data Sourced
via NVD·12:16 AM
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-53648?

CVE-2026-53648 has a risk score of 33, indicating a moderate severity level.

2

How can I fix CVE-2026-53648?

To fix CVE-2026-53648, upgrade to FOSSBilling version 0.8.1 or later.

3

What causes CVE-2026-53648?

CVE-2026-53648 is caused by filename collisions due to deterministic storage paths for uploaded product files.

4

What impact does CVE-2026-53648 have on FOSSBilling?

CVE-2026-53648 allows attackers to overwrite downloadable product files, potentially leading to unauthorized access or content manipulation.

5

Who is affected by CVE-2026-53648?

Any user or administrator of FOSSBilling versions prior to 0.8.1 is affected by CVE-2026-53648.

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