# CVE-2026-53640: Missing authorization in FOSSBilling

> Low-privileged staff can access sensitive data via unprotected read-only admin API endpoints in FOSSBilling.

- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Jul 2026
- **Updated:** 7 Jul 2026
- **Also known as:** GHSA-jqw4-3hj3-8m4f

## What is CVE-2026-53640?

CVE-2026-53640 is a low-severity missing authorization vulnerability in FOSSBilling, published on 6 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

FOSSBilling is a free, open-source billing and client management system. Prior to version 0.8.0, low-privileged staff accounts may read sensitive data via admin API endpoints that lack permission checks. While sibling write endpoints correctly enforce fine-grained permissions, the corresponding read endpoints have no authorization guards. Version 0.8.0 contains a fix. Some workarounds are available. Restrict staff accounts to only those who need access to sensitive data and/or use a reverse proxy or WAF to restrict access to the affected endpoints.

Weakness: CWE-862 (Missing Authorization), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-53640?


## How do I fix CVE-2026-53640?

No fix has been published for CVE-2026-53640 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-53640 being exploited?

There is no known exploitation of CVE-2026-53640 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-53640 and fix it if it is affected.

What it is: CVE-2026-53640 is a low-severity missing authorization vulnerability in FOSSBilling, published on 6 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-53640 in the wild and no public exploit code.

Affected product: FOSSBilling. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-53640/ (Markdown: https://insights.sbomify.com/CVE-2026-53640/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-53640
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-53640
- OSV: https://osv.dev/vulnerability/CVE-2026-53640

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-53640/
Summaries are generated and may contain mistakes; the official description above is the record.