Quick answers
- Is CVE-2026-53642 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-53642 being exploited in the wild.
- How severe is CVE-2026-53642?
- Informational severity, with a CVSS score of 5.3, published 6 July 2026.
- Which products and versions are affected?
- FOSSBilling >= 0.5.6, <= 0.7.2.
- Is there a fix for CVE-2026-53642?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-53642 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-53642?
- Check whether you run FOSSBilling at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
An incorrect authorization vulnerability exists in FOSSBilling's page-side enforcement logic within src/di.php. While API endpoints are correctly restricted via an allowlist, the routing logic for web pages uses an overly permissive check that allows any request path starting with '/client' for unverified users (email_approved = 0). This allows authenticated but unverified attackers to bypass the email confirmation gate and access sensitive routes such as /client/balance, /client/invoice, and /client/support/tickets. The vulnerability was introduced in PR #1534 and is resolved in version 0.8.0 by tightening the path-based access controls.
Affected products
- FOSSBilling FOSSBilling >= 0.5.6, <= 0.7.2
Timeline
- 2026-06-12: advisory: GitHub Security Advisory published
- 2026-07-06: disclosed: NVD publication date