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() 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.
CVE-2026-53648
This medium-severity CVE scores 5.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 82% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.1
- EG Score
- 5.1(medium)
- EPSS
- 17.9%
- KEV
- Not listed
Published
July 6, 2026
Last Modified
July 7, 2026
Advisory Details (1)
Auto-updated Jul 7, 2026Downloadable product files can be overwritten through filename collisions · Advisory · FOSSBilling/FOSSBilling · GitHub
https://github.com/FOSSBilling/FOSSBilling/security/advisories/GHSA-x7p2-xhvc-cfp9Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 16× in last 7d / 16× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-11 14:11 UTCEG score recompute
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-10 16:01 UTCEG score recompute
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-09 17:55 UTCEG score recompute
- 2026-07-08 19:50 UTCEG score recompute
- 2026-07-08 15:16 UTCEPSS rescore
- 2026-07-08 15:16 UTCEPSS rescore
- 2026-07-07 21:41 UTCEG score recompute
- 2026-07-07 13:46 UTCEPSS rescore
- 2026-07-07 13:46 UTCEPSS rescore
- 2026-07-06 23:36 UTCEG score recompute
- 2026-07-06 23:35 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-668 · CWE-73
- CVE-2019-16541EG 9.9CRITICAL
- CVE-2014-125059NVD 5.0EG 9.8MEDIUM
- CVE-2014-125044NVD 6.3EG 9.8MEDIUM
- CVE-2019-10781EG 9.8CRITICAL
- CVE-2008-7291EG 9.8CRITICAL
- CVE-2019-12929EG 9.8EPSS 91%CRITICAL
- CVE-2019-12928EG 9.8EPSS 97%CRITICAL
- CVE-2018-7846EG 9.8EPSS 98%CRITICAL
- CVE-2018-18068EG 9.8CRITICAL
- CVE-2018-17246EG 9.8EPSS 100%CRITICAL
Frequently asked(5)
What is CVE-2026-53648?
When was CVE-2026-53648 disclosed?
Is CVE-2026-53648 actively exploited?
What is the CVSS score of CVE-2026-53648?
How do I remediate CVE-2026-53648?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-53648
Is Your Infrastructure Affected by CVE-2026-53648?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.