CVE-2026-27708

HIGHPre-NVD 7.17.1
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (28th 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
7.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 7.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

FOSSBilling is a free, open-source billing and client management system. In versions 0.7.2 and prior, the Servicecustom Client API's __call method accepts an order_id parameter and fetches the associated order without verifying the authenticated client owns it, potentially exposing cross-client data through IDOR. An authenticated client can access any other client's custom service by guessing sequential order IDs. This can lead to a confidentiality breach — attackers can read client PII (name, email, phone, address, company details, VAT number) and service configuration data belonging to other clients. This issue has been fixed in version 0.8.0.

CVSS v3
7.1
EG Score
7.1HIGHmedium confidence
EG Risk
32
EG Risk 32/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)
Severity71% × 45%
The EG Score, 7.1 of 10.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). 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.
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* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). 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

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

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” 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 24, 2026

Last Modified

June 25, 2026

Advisory Details (2)

Auto-updated Jun 24, 2026
Patch available. Sources: github_release, github.
GitHub advisoryMentions a patch (unverified)

IDOR in Servicecustom client API allows cross-client data access · Advisory · FOSSBilling/FOSSBilling · GitHub

https://github.com/FOSSBilling/FOSSBilling/security/advisories/GHSA-p36w-9x66-488j
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(3)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 28× 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 96 of 151 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. 4 repeat rows among the latest 100 are merged into the row they repeat. The 55 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-27708?
CVE-2026-27708 is a high-severity vulnerability; its CVE record was published on June 24, 2026. FOSSBilling is a free, open-source billing and client management system. In versions 0.7.2 and prior, the Servicecustom Client API's call method accepts an order_id parameter and fetches the associated order without verifying the authenticated client owns it, potentially exposing cross-client data…
When was the CVE record for CVE-2026-27708 published?
The CVE record for CVE-2026-27708 was published on June 24, 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 June 25, 2026; the record at its source may have been updated since.
Is CVE-2026-27708 actively exploited?
CVE-2026-27708 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-2026-27708?
CVE-2026-27708 has a CVSS base score of 7.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-27708?
A fix for CVE-2026-27708 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-2026-27708

Explore →

Is Your Infrastructure Affected by CVE-2026-27708?

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

Book a Demo →Browse All CVEs