Vulnerabilidades do FOSSBilling FOSSBilling
🔔 Criar alerta RSS Verificador de versão
CVEs publicadas que afetam FOSSBilling FOSSBilling: 30 registro(s), com versões afetadas e correções.
CVE-2026-28496
Crítica · 9.4
Exploit público CWE-1336 23/06/2026
FOSSBilling: Server-Side Template Injection na renderização de templates Twig
FOSSBilling é um sistema gratuito e de código aberto para faturamento e gerenciamento de clientes. Versões anteriores à 0.8.0 possuem uma vulnerabilidade de Server-Side Template Injection (SSTI) no sistema de renderização de templates. Administradores com acesso a funcionalidades que renderizam templates Twig (templates de e-mail, campanhas de e-mail em massa, adaptadores de pagamento personalizados e o endpoint de API string_render) podem injetar expressões Twig arbitrárias, levando a divulgação de informações e execução remota de código. A vulnerabilidade existe porque os templates Twig são renderizados sem sandbox, permitindo acesso a todo o ambiente Twig, ao contexto da API e ao contêiner de injeção de dependências da aplicação. A versão 0.8.0 corrige o problema. Há algumas medidas de contorno disponíveis. Auditar os templates de e-mail existentes em busca de expressões Twig suspeitas, rotacionar todos os tokens de API de administradores e clientes, e/ou bloquear acesso externo a /api/system/* no proxy reverso/WAF para mitigar o encadeamento com GHSA-78x5-c8gw-8279.
CVE-2026-27604
Crítica · 10.0
Exploit público CWE-200 23/06/2026
FOSSBilling: bypass de autorização expõe endpoints privilegiados de sistema da API
O FOSSBilling é um sistema gratuito e de código aberto para cobrança e gestão de clientes. A partir da versão 0.5.4 e antes da versão 0.8.0, um bypass de autorização no tratamento de papéis da API permite acesso não autenticado a endpoints privilegiados /api/system/*. Como system resolve para a identidade de administrador do cron, atacantes podem invocar métodos administrativos da API sem credenciais válidas, sessão ou token CSRF. A versão 0.8.0 corrige o problema. Estão disponíveis algumas medidas de contorno: bloquear o acesso externo a /api/system/* no proxy reverso ou WAF, restringir o acesso à API somente a IPs confiáveis (api.allowed_ips), rotacionar imediatamente todos os tokens de API de administradores e clientes, invalidar sessões ativas e redefinir credenciais de alto privilégio, e/ou revisar os logs de requisições da API em busca de acessos suspeitos a /api/system/ e tratar o caso como potencial incidente.
CVE-2026-43926
Média · 6.3
CWE-204 04/06/2026
FOSSBilling's password reset confirmation endpoint lacks rate limiting
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', random_bytes(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.
CVE-2026-43924
Média · 4.8
CWE-601 03/06/2026
FOSSBilling has an open redirect via administrator-configured redirect targets
FOSSBilling is a free, open-source billing and client management system. Prior to version 0.8.0, the Redirect module does not validate the URL scheme of administrator-configured destination URLs before storing or issuing redirects. This allows arbitrary external URLs to be configured as redirect targets, creating an open redirect vulnerability exploitable for phishing attacks. Users following a legitimate FOSSBilling URL can be silently redirected to an attacker-controlled external site. The redirect is issued as a 301 (Moved Permanently) response, which browsers cache persistently, amplifying the impact. Exploitation requires administrator privileges to create or modify redirect entries, limiting practical attack scenarios to multi-admin environments or compromised admin accounts. Version 0.8.0 fixes the issue. Some workarounds are available. Restrict admin access to the Redirect module to trusted administrators only and/or audit existing redirect entries in the database (the `extension_meta` table with `extension = 'mod_redirect'`) for any unexpected or external target URLs.
CVE-2026-40495
Média · 6.9
CWE-200 03/06/2026
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 `hide_version_public` security setting. The FOSSBilling version is embedded in the query string of every `<script>` and `<link>` tag generated by the `script_tag` and `stylesheet_tag` Twig filters. This information is visible to all visitors — including unauthenticated guests — on every page, regardless of whether the `hide_version_public` setting is enabled. The `X-FOSSBilling-Version` HTTP header and the `guest.system.version` API endpoint correctly honour the `hide_version_public` 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 `hide_version_public` 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.