CVE-2025-64105

MEDIUMPre-NVD 5.15.1—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (27th percentile of EPSS-scored CVEs). 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
5.1EG
EchelonGraph verdictMonitorRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 5.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

FOSSBilling is a billing and client management system that automates invoicing, payments, and communication for online service businesses. Versions 0.6.21 through 0.7.2 are vulnerable to IDOR through the support ticket creation workflow. By manipulating rel_id when rel_type=order, an authenticated client can create a support ticket that references another client's order they do not own. The ticketCreateForClient() method accepted rel_id without verifying order ownership for non-upgrade tasks, allowing clients to link a new ticket to another client's order by crafting the request. No cron task automatically processes cancel/upgrade requests from ticket relations; staff action is required. This affects integrity and confidentiality: staff could be misled into acting on the wrong order (e.g., cancellation or upgrade requests). While there is no client-to-client order data exposure, order IDs may appear in ticket context. This issue has been fixed in version 0.8.0.

CVSS v3
5.1
EG Score
5.1MEDIUMmedium confidence
EG Risk
28
EG Risk 28/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity51% × 45%
The EG Score, 5.1 of 10.
Exploitation0% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability30% × 15%
EchelonGraph's default: CISA has not published Automatable for this CVE.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
28th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track or Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

Published

June 23, 2026

Last Modified

October 5, 2026

Advisory Details (2)

Auto-updated Jun 25, 2026
Patch available. Sources: github_release, github.
githubMentions a patch (unverified)

Support ticket order relation IDOR allows cross‑client order references · Advisory · FOSSBilling/FOSSBilling · GitHub

https://github.com/FOSSBilling/FOSSBilling/security/advisories/GHSA-rcr8-p92p-9887
github_release Patch Available

0.8.0

Patch available: FOSSBilling/FOSSBilling 0.8.0

https://github.com/FOSSBilling/FOSSBilling/releases/tag/0.8.0

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 29× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 95 of 148 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 5 repeat rows among the latest 100 are merged into the row they repeat. The 53 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  2. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  3. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  4. 2026-10-08 17:10 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  5. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  6. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  7. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  8. 2026-10-05 16:29 UTCEG score recompute
  9. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  10. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  11. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  12. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  13. 2026-09-29 15:20 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  14. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  15. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  16. 2026-09-24 14:02 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  17. 2026-09-23 13:47 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  18. 2026-09-23 11:58 UTCEG score recompute
  19. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  20. 2026-09-19 15:42 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  21. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  22. 2026-09-18 10:23 UTCEG score recompute
  23. 2026-09-17 19:30 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  24. 2026-09-16 14:07 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  25. 2026-09-15 03:10 UTCEPSS rescoreEPSS 0.4% · 29th percentile
Show 70 more
  1. 2026-09-13 16:46 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  2. 2026-09-13 12:21 UTCEG score recompute
  3. 2026-09-12 15:00 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  4. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  5. 2026-09-11 09:36 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  6. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  7. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  8. 2026-09-07 16:00 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  9. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  10. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  11. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  12. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  13. 2026-08-30 20:25 UTCEG score recompute
  14. 2026-08-30 19:16 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  15. 2026-08-30 01:21 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  16. 2026-08-28 21:40 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  17. 2026-08-27 14:24 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  18. 2026-08-26 14:45 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  19. 2026-08-25 13:48 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  20. 2026-08-24 22:05 UTCEG score recompute
  21. 2026-08-24 14:16 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  22. 2026-08-23 15:18 UTCEG score recompute
  23. 2026-08-23 00:18 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  24. 2026-08-22 13:45 UTCEG score recompute
  25. 2026-08-21 23:48 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  26. 2026-08-21 09:19 UTCEG score recompute
  27. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  28. 2026-08-20 07:45 UTCEG score recompute
  29. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  30. 2026-08-19 04:48 UTCEG score recompute
  31. 2026-08-18 13:47 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  32. 2026-08-17 13:46 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  33. 2026-08-17 11:51 UTCEG score recompute
  34. 2026-08-16 14:55 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  35. 2026-08-16 10:18 UTCEG score recompute
  36. 2026-08-16 02:13 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  37. 2026-08-15 08:45 UTCEG score recompute
  38. 2026-08-15 01:29 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  39. 2026-08-14 05:51 UTCEG score recompute
  40. 2026-08-13 21:59 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  41. 2026-08-13 04:17 UTCEG score recompute
  42. 2026-08-12 13:50 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  43. 2026-08-12 02:44 UTCEG score recompute
  44. 2026-08-11 13:42 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  45. 2026-08-11 01:11 UTCEG score recompute
  46. 2026-08-10 23:59 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  47. 2026-08-09 23:38 UTCEG score recompute
  48. 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  49. 2026-08-08 22:05 UTCEG score recompute
  50. 2026-08-08 16:36 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  51. 2026-08-07 20:31 UTCEG score recompute
  52. 2026-08-07 16:26 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  53. 2026-08-06 18:58 UTCEG score recompute
  54. 2026-08-06 13:46 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  55. 2026-08-05 19:17 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  56. 2026-08-04 15:14 UTCEG score recompute
  57. 2026-08-04 15:09 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  58. 2026-08-04 10:37 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  59. 2026-08-03 10:35 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  60. 2026-08-02 07:42 UTCEG score recompute
  61. 2026-08-02 02:26 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  62. 2026-08-01 06:08 UTCEG score recompute
  63. 2026-08-01 04:15 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  64. 2026-07-31 04:22 UTCEG score recompute
  65. 2026-07-30 16:27 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  66. 2026-07-30 02:49 UTCEG score recompute
  67. 2026-07-30 01:30 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  68. 2026-07-29 01:15 UTCEG score recompute
  69. 2026-07-28 15:35 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  70. 2026-07-27 17:45 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2025-64105?
CVE-2025-64105 is a medium vulnerability published on June 23, 2026. FOSSBilling is a billing and client management system that automates invoicing, payments, and communication for online service businesses. Versions 0.6.21 through 0.7.2 are vulnerable to IDOR through the support ticket creation workflow. By manipulating relid when reltype=order, an authenticated…
When was the CVE record for CVE-2025-64105 published?
The CVE record for CVE-2025-64105 was published on June 23, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 5, 2026; the record at its source may have been updated since.
Is CVE-2025-64105 actively exploited?
CVE-2025-64105 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (28th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-64105?
CVE-2025-64105 has a CVSS base score of 5.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2025-64105?
A fix for CVE-2025-64105 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2025-64105

Explore →

Is Your Infrastructure Affected by CVE-2025-64105?

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

Book a Demo →Browse All CVEs