CVE-2026-40495: FOSSBilling version exposed via asset cache buster
FOSSBilling is a free, open-source billing and client management system. Versions prior to 0.8.0 leak the exact system version through asset cache buster parameters in HTML output, bypassing the hideversionpublic security setting. The FOSSBilling version is embedded in the query string of every <script> and <link> tag generated by the scripttag and stylesheettag Twig filters. This information is visible to all visitors — including unauthenticated guests — on every page, regardless of whether the hideversionpublic setting is enabled. The X-FOSSBilling-Version HTTP header and the guest.system.version API endpoint correctly honour the hideversionpublic setting, but the asset cache buster parameters were overlooked. Knowledge of the exact FOSSBilling version makes it significantly easier for malicious actors to identify known vulnerabilities applicable to a given installation and craft targeted exploits. While not a direct vulnerability on its own, it undermines the intended protection offered by the hideversionpublic setting and facilitates reconnaissance. Version 0.8.0 contains a patch. There is no practical workaround that removes the version from asset URLs without modifying source code.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
FOSSBillingto a version that resolves this vulnerability.Fixed in 0.8.0
Event History
Frequently Asked Questions
What is the severity of CVE-2026-40495?
The severity of CVE-2026-40495 is medium with a CVSS score of 6.9.
How do I fix CVE-2026-40495?
To fix CVE-2026-40495, upgrade FOSSBilling to version 0.8.0 or later.
What type of vulnerability is CVE-2026-40495?
CVE-2026-40495 is classified as an information leak vulnerability.
What causes CVE-2026-40495?
CVE-2026-40495 is caused by FOSSBilling versions prior to 0.8.0 leaking the system version through asset cache buster parameters in HTML output.
Is there a public disclosure for CVE-2026-40495?
Yes, CVE-2026-40495 was publicly disclosed on June 3, 2026.