FOSSBilling is a free, open-source billing and client management system. Prior to version 0.8.0, the Guest API invoice/update endpoint is missing an authorization check present in other invoice-related endpoints, allowing an unauthenticated user with knowledge of an invoice hash to modify the payment gateway associated with an unpaid invoice. An attacker who obtains an invoice hash, which may leak through shared URLs, referrer headers, or email links, can change the gateway_id on an unpaid invoice to any payment gateway configured in the system. This does not allow redirecting payments to an arbitrary external endpoint, as the gateway must already be installed and configured by an administrator. The practical impact is further limited by the invoice_accessible_from_hash system setting. Version 0.8.0 contains a patch. No known workarounds are available.
CVE-2026-42331
This high-severity CVE scores 7.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 84% 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).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.7
- EG Score
- 7.7(medium)
- EPSS
- 15.9%
- KEV
- Not listed
Published
July 6, 2026
Last Modified
July 7, 2026
Advisory Details (1)
Auto-updated Jul 7, 2026Missing authorization in guest Invoice API endpoints · Advisory · FOSSBilling/FOSSBilling · GitHub
https://github.com/FOSSBilling/FOSSBilling/security/advisories/GHSA-8755-w77f-3g7jWeakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 21× in last 7d / 23× 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.
- 2026-07-14 00:24 UTCEG score recompute
- 2026-07-13 22:30 UTCEPSS rescore
- 2026-07-13 12:10 UTCEG score recompute
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-12 23:55 UTCEG score recompute
- 2026-07-12 11:41 UTCEG score recompute
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-11 23:26 UTCEG score recompute
- 2026-07-11 11:12 UTCEG score recompute
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-10 22:58 UTCEG score recompute
- 2026-07-10 10:44 UTCEG score recompute
- 2026-07-09 22:30 UTCEG score recompute
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-09 10:16 UTCEG score recompute
- 2026-07-08 22:01 UTCEG score recompute
- 2026-07-08 15:15 UTCEPSS rescore
- 2026-07-08 09:48 UTCEG score recompute
- 2026-07-07 21:34 UTCEG score recompute
- 2026-07-07 13:46 UTCEPSS rescore
- 2026-07-07 09:20 UTCEG score recompute
- 2026-07-06 21:05 UTCEG score recompute
- 2026-07-06 21:04 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-306 · CWE-863
Frequently asked(5)
What is CVE-2026-42331?
When was CVE-2026-42331 disclosed?
Is CVE-2026-42331 actively exploited?
What is the CVSS score of CVE-2026-42331?
How do I remediate CVE-2026-42331?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-42331
Is Your Infrastructure Affected by CVE-2026-42331?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.