CVE-2026-53645

HIGHPre-NVD 8.58.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 85% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
8.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

FOSSBilling is a free, open-source billing and client management system. Versions prior to 0.8.0 allow a low-privileged staff account to grant arbitrary module permissions to itself through the admin API, resulting in persistent privilege escalation. A staff user that only has staff.create_and_edit_staff can call /api/admin/staff/permissions_update targeting their own account and write any permission structure, bypassing the intended role-based access control boundary. Version 0.8.0 patches the issue. Some workarounds are available. Restrict the staff.create_and_edit_staff permission to only highly trusted staff members and/or use a reverse proxy or WAF to restrict access to /api/admin/staff/permissions_update to specific trusted roles.

CVSS v3
8.5
EG Score
8.5(medium)
EPSS
15.0%
KEV
Not listed

Published

July 6, 2026

Last Modified

July 7, 2026

Advisory Details (1)

Auto-updated Jul 7, 2026
Patch available. Sources: github.
github Patch Available

Missing self-edit prevention in staff permission management allows persistent privilege escalation · Advisory · FOSSBilling/FOSSBilling · GitHub

https://github.com/FOSSBilling/FOSSBilling/security/advisories/GHSA-4hf7-xxxw-64rm

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 25× in last 7d / 35× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-15 23:59 UTCEG score recompute
  2. 2026-07-15 16:57 UTCEPSS rescore
  3. 2026-07-15 16:57 UTCEPSS rescore
  4. 2026-07-15 11:15 UTCEG score recompute
  5. 2026-07-15 02:00 UTCEPSS rescore
  6. 2026-07-15 02:00 UTCEPSS rescore
  7. 2026-07-14 22:27 UTCEG score recompute
  8. 2026-07-14 09:43 UTCEG score recompute
  9. 2026-07-13 22:31 UTCEPSS rescore
  10. 2026-07-13 20:59 UTCEG score recompute
  11. 2026-07-13 08:14 UTCEG score recompute
  12. 2026-07-13 06:13 UTCEPSS rescore
  13. 2026-07-13 06:13 UTCEPSS rescore
  14. 2026-07-12 19:28 UTCEG score recompute
  15. 2026-07-12 06:44 UTCEG score recompute
  16. 2026-07-12 05:46 UTCEPSS rescore
  17. 2026-07-11 17:57 UTCEG score recompute
  18. 2026-07-11 08:27 UTCEPSS rescore
  19. 2026-07-11 08:27 UTCEPSS rescore
  20. 2026-07-11 05:13 UTCEG score recompute
  21. 2026-07-10 16:27 UTCEG score recompute
  22. 2026-07-10 03:42 UTCEG score recompute
  23. 2026-07-09 19:10 UTCEPSS rescore
  24. 2026-07-09 19:10 UTCEPSS rescore
  25. 2026-07-09 14:57 UTCEG score recompute
Show 10 more
  1. 2026-07-09 02:11 UTCEG score recompute
  2. 2026-07-08 15:16 UTCEPSS rescore
  3. 2026-07-08 15:16 UTCEPSS rescore
  4. 2026-07-08 13:26 UTCEG score recompute
  5. 2026-07-08 00:41 UTCEG score recompute
  6. 2026-07-07 13:46 UTCEPSS rescore
  7. 2026-07-07 13:46 UTCEPSS rescore
  8. 2026-07-07 11:56 UTCEG score recompute
  9. 2026-07-06 23:11 UTCEG score recompute
  10. 2026-07-06 23:10 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-53645?
CVE-2026-53645 is a high vulnerability published on July 6, 2026. FOSSBilling is a free, open-source billing and client management system. Versions prior to 0.8.0 allow a low-privileged staff account to grant arbitrary module permissions to itself through the admin API, resulting in persistent privilege escalation. A staff user that only has…
When was CVE-2026-53645 disclosed?
CVE-2026-53645 was first published in the National Vulnerability Database on July 6, 2026, with the most recent update on July 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53645 actively exploited?
CVE-2026-53645 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 15.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-53645?
CVE-2026-53645 has a CVSS v3 base score of 8.5 (NVD).
How do I remediate CVE-2026-53645?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53645, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-53645

Explore →

Is Your Infrastructure Affected by CVE-2026-53645?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs