CVE-2026-59235

HIGHPre-NVD 8.78.7
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.7% (50th 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
Trending — 3 sources updated this week
8.7EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 8.7Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Fixed versions, as the CVE record's CNA (Secur0) states them: "Upgrade to version 5.5.3 or higher."

Missing Authorization (CWE-862) in BankAccountListController (app/Http/Controllers/Api/BankAccount/BankAccountListController.php), exposed at GET /api/bank-account, in Prospero Flow CRM <5.5.3, which allows a remote, authenticated attacker holding a low-privileged role (e.g. the "User"/"Usuario" role) to read arbitrary bank account records belonging to their company by sending an authenticated request to the endpoint with a valid bearer token, because the API route is protected only by the auth:api middleware and carries no permission gate, unlike the equivalent web route, which enforces can('read bank'), and the handler resolves records with Account::where('company_id', Auth::user()->company_id)->get(), performing only company scoping and no role or permission check before returning the data. This results in the unauthorized disclosure of sensitive banking information (e.g. IBAN, SWIFT/BIC, account identifiers) to users who should not have access to it.

CVSS v3
8.7
EG Score
8.7HIGHmedium confidence
EG Risk
54
EG Risk 54/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)
Severity87% × 45%
The EG Score, 8.7 of 10.
Exploitation0.7% × 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.7%
EPSS %ILE
50th
KEV
Not listed

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.

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

July 15, 2026

Last Modified

July 15, 2026

Advisory Details (3)

Auto-updated Jul 15, 2026
Patch available. Sources: github_commit.
Web page

CVE-2026-59235 · Missing authorization in Prospero Flow CRM allows low-privileged users to read all bank accounts | Vulnerabilities published by Secur0

https://secur0.com/en/cna/cve-list/cve-2026-59235-missing-authorization-in-prospero-flow-crm-allows-low-privileged-users-to-read-all-bank-accounts
Web page

Releases · Roskus/prospero-flow-crm · GitHub

https://github.com/Roskus/prospero-flow-crm/releases#release-v5.5.3
GitHub commit Patch Available

commit 57bb57212af0 (Roskus/prospero-flow-crm)

Patch available: Roskus/prospero-flow-crm v5.5.3 (contains commit 57bb57212af0)

https://github.com/Roskus/prospero-flow-crm/commit/57bb57212af03151c989d67d6723d5ddb3e81e7b

Vendor Advisories for CVE-2026-59235(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 13× in last 7d / 42× 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 100 of 223 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. None are among the latest 100 rows. The 123 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-59235?
CVE-2026-59235 is a high-severity vulnerability; its CVE record was published on July 15, 2026. Missing Authorization (CWE-862) in BankAccountListController (app/Http/Controllers/Api/BankAccount/BankAccountListController.php), exposed at GET /api/bank-account, in Prospero Flow CRM <5.5.3, which allows a remote, authenticated attacker holding a low-privileged role (e.g. the "User"/"Usuario"…
When was CVE-2026-59235 made public?
CVE-2026-59235 was made public on July 15, 2026: that is the date its CVE record's CNA, Secur0, gives for when the vulnerability was made public. The CVE record itself was published on July 15, 2026. EchelonGraph's copy of the record carries a last-modified date of July 15, 2026; the record at its source may have been updated since.
Is CVE-2026-59235 actively exploited?
CVE-2026-59235 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (50th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-59235?
CVE-2026-59235 has a CVSS base score of 8.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-59235?
A fix for CVE-2026-59235 is available: update to the fixed version the vendor names in its advisory. Fixed versions, as the CVE record's CNA (Secur0) states them: "Upgrade to version 5.5.3 or higher." The vendor advisories EchelonGraph has for CVE-2026-59235 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-59235?

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

Book a Demo →Browse All CVEs