CVE-2026-43926: FOSSBilling's password reset confirmation endpoint lacks rate limiting

Published Jun 4, 2026
·
Updated

FOSSBilling is a free, open-source billing and client management system. Prior to version 0.8.0, the password reset confirmation endpoint /client/reset-password-confirm/:hash is handled by a non-API controller and is not covered by FOSSBilling's rate limiter, which only applies to /api/ routes. This allows an attacker to probe the endpoint for valid reset tokens without any per-IP request limiting, attempt counting, or lockout mechanism. The endpoint acts as an oracle, returning a distinguishable response for valid versus invalid tokens (HTTP 200 vs HTTP 302 redirect). An attacker can submit unlimited token guesses to the password reset confirmation endpoint with no throttling applied. However, practical exploitability is significantly mitigated by the current token generation, which uses hash('sha256', randombytes(32)), providing 256 bits of entropy. Tokens also expire after 15 minutes and are deleted after successful use. The same architectural gap applies to other controller-served auth routes, including /staff/email/:hash (admin password reset confirmation) and /client/confirm-email/:hash (email confirmation). Version 0.8.0 fixes the issue. Some workarounds are available. Configure a reverse proxy (e.g., Nginx, Apache, Cloudflare) to apply per-IP rate limiting to the /client/reset-password-confirm/ and /staff/email/ paths and/or use a WAF rule to limit request rates to these endpoints.

Affected Software

1 affected component
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. Compensating control

    Configure a reverse proxy (e.g., Nginx, Apache, Cloudflare) or a WAF to apply per-IP request rate limiting for the following controller-served endpoints that lack rate limiting: /client/reset-password-confirm/*, /staff/email/*, and /client/confirm-email/*.

Event History

Jun 4, 2026
CVE Published
via MITRE·12:46 PM
Data Sourced
via MITRE·12:46 PM
DescriptionWeakness
Data Sourced
via NVD·02: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-43926?

CVE-2026-43926 has a medium severity score of 6.3.

2

How do I fix CVE-2026-43926?

To fix CVE-2026-43926, update FOSSBilling to version 0.8.0 or later.

3

What component is affected by CVE-2026-43926?

CVE-2026-43926 affects the password reset confirmation endpoint of FOSSBilling before version 0.8.0.

4

Is there a known exploit for CVE-2026-43926?

CVE-2026-43926 does not have a publicly available exploit, but the lack of rate limiting may allow brute-force attacks.

5

What consequences might arise from CVE-2026-43926?

CVE-2026-43926 could lead to unauthorized access to user accounts through brute-force attempts on password resets.

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