CVE-2025-64105

MEDIUMPre-NVD 5.15.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This medium-severity CVE scores 5.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (30th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source

Also known asEUVD-2025-210325 (ENISA EUVD)Source: ENISA EUVD

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
38
EG Risk 38/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity51% × 45%
Impact severity (EG Severity): CVSS 5.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (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
30th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (5.1): severity, escalated by confirmed exploitation. This CVE's 5.1 is its impact severity (EG Severity), not escalated.

EG Severity
5.1 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; 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 (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (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

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

June 23, 2026

Last Modified

October 12, 2026

Advisory Details (2)

Auto-updated Jun 25, 2026
Patch available. Sources: github_release, github.
GitHub advisoryMentions 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 8× in last 7d / 40× 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 97 of 181 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. 3 repeat rows among the latest 100 are merged into the row they repeat. The 84 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2025-64105?
CVE-2025-64105 is a medium-severity vulnerability; its CVE record was 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 rel_id when rel_type=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 12, 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 (30th 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.