dbcve.org
Information ExposureWeakness · CWE-200

CVE-2026-53647

MEDIUM · 6.9 CVSS v4.0 Published 2026-07-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges Zero-click 6 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

FOSSBilling versions 0.5.3-0.7.2 have an unauthenticated information disclosure vulnerability in the Guest serviceapikey/get_info API endpoint. While the endpoint requires a valid API key to be provided by the caller, it lacks proper authentication verification, allowing retrieval of all custom_* configuration fields stored in the API key record.

MitigationUpgrade to FOSSBilling version 0.8.0 which patches the authentication bypass. As interim measures, avoid storing sensitive data in custom_* API key fields, monitor API logs for unauthorized access to /api/guest/serviceapikey/get_info, or disable the Serviceapikey module if unused.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed FOSSBilling version
    Locate the version file (typically version.php or similar in the installation root) or check the admin dashboard 'About' page. Compare the version number against the affected range 0.5.3 to 0.7.2.
    Affected if Installed version is 0.5.3, 0.5.4, 0.6.0, 0.6.1, 0.7.0, 0.7.1, or 0.7.2 (any version from 0.5.3 through 0.7.2 inclusive).
  2. Verify Serviceapikey module is enabled
    In the FOSSBilling admin panel, navigate to Settings > Modules (or equivalent) and check if the 'serviceapikey' or 'Service API Key' module is active. Alternatively, inspect the modules directory for the serviceapikey folder and check its manifest status.
    Affected if The Serviceapikey module is installed and enabled.
  3. Inspect API key records for custom_ fields
    Access the database (via phpMyAdmin or CLI) and query the api_key table. Look for records containing fields prefixed with 'custom_' that may hold sensitive values (passwords, tokens, secrets).
    Affected if Any API key record contains custom_* fields with sensitive or confidential data.
  4. Review API access logs for the vulnerable endpoint
    Examine FOSSBilling logs (typically in /logs/ or via the admin panel's logging feature) for requests to /api/guest/serviceapikey/get_info. Look for unauthorized or unexpected accesses.
    Affected if Logs show access to /api/guest/serviceapikey/get_info from untrusted sources or without proper authentication context.

You are affected if FOSSBilling version is 0.5.3 through 0.7.2, the Serviceapikey module is enabled, and sensitive data exists in custom_* API key fields that could be disclosed via the unauthenticated endpoint.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to FOSSBilling version 0.8.0 which patches the authentication bypass. As interim measures, avoid storing sensitive data in custom_* API key fields, monitor API logs for unauthorized access to /api/guest/serviceapikey/get_info, or disable the Serviceapikey module if unused.

Recommended fix High confidence

FOSSBilling version 0.8.0

  1. Upgrade FOSSBilling to version 0.8.0 or later to resolve the authentication bypass vulnerability
  2. After upgrading, verify that the /api/guest/serviceapikey/get_info endpoint now requires proper authentication
  3. As a configuration workaround, avoid storing sensitive business data in custom_* API key configuration fields
  4. Monitor API access logs for any suspicious or unauthorized calls to /api/guest/serviceapikey/get_info
  5. If the Serviceapikey module is not actively used, disable it via the admin panel to reduce attack surface

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,620
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,592.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-53647 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-53647 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data