Answer in brief
CVE-2026-27604 records a Critical severity (CVSS 10.0) vulnerability in FOSSBilling: Improper API Role Validation (system) Enables Unauthenticated Access to Privileged Admin Functions. The current sources do not mark it as known exploited. The current feed maps FOSSBilling/FOSSBilling (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 10.0. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps FOSSBilling/FOSSBilling (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| FOSSBilling/FOSSBillinggeneric | >= 0.5.4, < 0.8.0 | Not reported |
Published upstream
Jun 23, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Jun 23, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 23, 2026
FOSSBilling is a free, open-source billing and client management system. Starting in version 0.5.4 and prior to version 0.8.0, an authorization bypass in the API role handling allows unauthenticated access to privileged `/api/system/*` endpoints. Because `system` resolves to the cron admin identity, attackers can invoke admin API methods without valid credentials, session, or CSRF token. Version 0.8.0 patches the issue. Some workarounds are available. Block external access to `/api/system/*` at reverse proxy/WAF, restrict API access by trusted source IPs only (`api.allowed_ips`), rotate all admin/client API tokens immediately, invalidate active sessions and reset high-privilege credentials, and/or review API request logs for suspicious `/api/system/` access and treat as potential incident.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-27604 records a Critical severity (CVSS 10.0) vulnerability in FOSSBilling: Improper API Role Validation (system) Enables Unauthenticated Access to Privileged Admin Functions. The current sources do not mark it as known exploited. The current feed maps FOSSBilling/FOSSBilling (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 10.0. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps FOSSBilling/FOSSBilling (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| FOSSBilling/FOSSBillinggeneric | >= 0.5.4, < 0.8.0 | Not reported |
Published upstream
Jun 23, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Jun 23, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 23, 2026
FOSSBilling is a free, open-source billing and client management system. Starting in version 0.5.4 and prior to version 0.8.0, an authorization bypass in the API role handling allows unauthenticated access to privileged `/api/system/*` endpoints. Because `system` resolves to the cron admin identity, attackers can invoke admin API methods without valid credentials, session, or CSRF token. Version 0.8.0 patches the issue. Some workarounds are available. Block external access to `/api/system/*` at reverse proxy/WAF, restrict API access by trusted source IPs only (`api.allowed_ips`), rotate all admin/client API tokens immediately, invalidate active sessions and reset high-privilege credentials, and/or review API request logs for suspicious `/api/system/` access and treat as potential incident.
Quoted source text, attributed separately from HOL analysis.