CVE-2026-53647
Received Received - Intake

Information Disclosure in FOSSBilling API Key Configuration

Publication date: 2026-07-07

Last updated on: 2026-07-07

Assigner: GitHub, Inc.

Description
FOSSBilling is a free, open-source billing and client management system. In versions 0.5.3 through 0.7.2, the Guest `serviceapikey/get_info` API endpoint is accessible without authentication. Any caller with a valid API key can retrieve all custom configuration parameters (`custom_*` fields) stored in the key's database record. These custom fields are populated by billing administrators and can contain business-sensitive data such as pricing tiers, feature flags, rate limits, expiry overrides, or access scope data. Version 0.8.0 patches the issue. Some workarounds are available. Administrators can avoid storing sensitive data in `custom_*` API key configuration fields, monitor API logs for suspicious calls to `/api/guest/serviceapikey/get_info`, and/or disable the Serviceapikey module if not in active use.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-07-07
Last Modified
2026-07-07
Generated
2026-07-07
AI Q&A
2026-07-07
EPSS Evaluated
N/A
NVD
CVE-2026-53647

Affected Vendors & Products

Showing 2 associated CPEs
Vendor Product Version / Range
fossbilling fossbilling From 0.5.3 (inc) to 0.7.2 (inc)
fossbilling fossbilling 0.8.0

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-200 The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
CWE-306 The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources.
CWE-862 The product does not perform an authorization check when an actor attempts to access a resource or perform an action.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-53647 is a vulnerability in FOSSBilling versions 0.5.3 through 0.7.2 where the Guest API endpoint serviceapikey/get_info is accessible without authentication.

This means that any caller with a valid API key can retrieve all custom configuration parameters (custom_* fields) stored in the API key's database record.

These custom fields may contain sensitive business information such as pricing tiers, feature flags, rate limits, expiry overrides, or access scope data.

The vulnerability exists because the get_info method does not verify ownership or administrative access before returning this data.

It is classified under exposure of sensitive information, missing authentication, and missing authorization weaknesses.

Impact Analysis

This vulnerability can lead to unauthorized disclosure of sensitive business data stored in the custom configuration fields of API keys.

An attacker or any user with a valid API key can access internal administrative settings such as pricing tiers, feature flags, rate limits, expiry overrides, or access scope data.

Exposure of this information could lead to competitive disadvantage, misuse of service features, or other business risks.

Since the vulnerability requires no privileges or user interaction and has low attack complexity, it is relatively easy to exploit.

Detection Guidance

This vulnerability can be detected by monitoring API logs for suspicious calls to the endpoint /api/guest/serviceapikey/get_info.

Administrators should look for any unauthorized or unusual access patterns to this endpoint, especially calls made without proper authentication.

A suggested command to detect such activity could be to search your web server or application logs for requests to this endpoint, for example using grep:

  • grep "/api/guest/serviceapikey/get_info" /path/to/your/api/logs/access.log

This command will help identify any calls made to the vulnerable API endpoint, which could indicate exploitation attempts.

Mitigation Strategies

Immediate mitigation steps include upgrading FOSSBilling to version 0.8.0 or later, where the vulnerability is patched.

If upgrading is not immediately possible, administrators can avoid storing sensitive data in the custom_* API key configuration fields.

Additionally, monitoring API logs for suspicious calls to /api/guest/serviceapikey/get_info can help detect exploitation attempts.

Another workaround is to disable the Serviceapikey module if it is not actively used in your environment.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-53647. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart